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
This commit is contained in:
Juan Antonio Osorio Robles 2017-04-12 14:31:53 +03:00
parent df36f221dd
commit 65e643aca2
2 changed files with 8 additions and 1 deletions

View File

@ -127,7 +127,7 @@ parameters:
type: comma_delimited_list type: comma_delimited_list
description: > description: >
Cron to purge expired tokens - Hour Cron to purge expired tokens - Hour
default: '0' default: '*'
KeystoneCronTokenFlushMonthday: KeystoneCronTokenFlushMonthday:
type: comma_delimited_list type: comma_delimited_list
description: > description: >

View File

@ -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.