configurable keystone-token-flush cronjob schedules

Bug #1729646 reported by Alvaro Uria
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Keystone Charm
Triaged
Wishlist
Unassigned

Bug Description

By default, keystone-token-flush cronjob runs once every hour (0 * * * *).

In the past, we have had trouble with long transactions locking the keystone.token table, degrading the service due to token timeouts and restoring normal operation by killing such transaction in mysql.

I would like to suggest a new config parameter to be able to run the cronjob every N minutes (ie. 10 minutes). Although token-expiration would be configured to 3600 or more, there would be tokens to delete within the hour, reducing the workload on larger clouds.

Sample:
juju config keystone token-cron-schedule='*/10 * * * *'

  token-cron-schedule:
    default: true
    description: |
      Cron schedule used to run keystone-manage token_flush.
      If unset, it will run once an hour
    type: string
    value: '0 * * * *'

James Page (james-page)
Changed in charm-keystone:
status: New → Triaged
importance: Undecided → Wishlist
Yamen Hatahet (yhatahet)
Changed in charm-keystone:
assignee: nobody → Yamen Hatahet (yhatahet)
Yamen Hatahet (yhatahet)
Changed in charm-keystone:
assignee: Yamen Hatahet (yhatahet) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.