From 65e643aca2202f031db94f1ccd3d44e195e5e772 Mon Sep 17 00:00:00 2001 From: Juan Antonio Osorio Robles Date: Wed, 12 Apr 2017 14:31:53 +0300 Subject: Run token flush cron job hourly by default Running this job once a day has proven problematic for large deployments as seen in the bug report. Setting it to run hourly would be an improvement to the current situation, as the flushes wouldn't need to process as much data. Note that this only affects people using UUID as the token provider. Change-Id: I462e4da2bfdbcba0403ecde5d613386938e2283a Related-Bug: #1649616 --- releasenotes/notes/token-flush-twice-a-day-d4b00a2953a6b383.yaml | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 releasenotes/notes/token-flush-twice-a-day-d4b00a2953a6b383.yaml (limited to 'releasenotes') diff --git a/releasenotes/notes/token-flush-twice-a-day-d4b00a2953a6b383.yaml b/releasenotes/notes/token-flush-twice-a-day-d4b00a2953a6b383.yaml new file mode 100644 index 00000000..70051f65 --- /dev/null +++ b/releasenotes/notes/token-flush-twice-a-day-d4b00a2953a6b383.yaml @@ -0,0 +1,7 @@ +--- +fixes: + - The token flush cron job has been modified to run hourly instead of once + a day. This is because this was causing issues with larger deployments, as + the operation would take too long and sometimes even fail because of the + transaction being so large. Note that this only affects people using the + UUID token provider. -- cgit 1.2.3-korg