High numbers of revocation events cause excessive cache churn
Bug #1220359 reported by
Morgan Fainberg
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Low
|
Morgan Fainberg |
Bug Description
Due to the explicit refresh on the revocation list cache, when a revocation event occurs there is an added extra load to the Keystone processes. This should be changed to an invalidate of cache to ensure that we do not have to regenerate the revocation_list except on actual demand. This reduces overall lock contention when using memcache / redis / external storage as the cache layer.
Changed in keystone: | |
importance: | Undecided → Low |
summary: |
- High revocation events cause excessive cache churn + High numbers of revocation events cause excessive cache churn |
Changed in keystone: | |
milestone: | none → havana-rc1 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/45806
Review: https:/