yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #36051
[Bug 1287757] Re: Optimization: Don't prune events on every get
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => liberty-2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1287757
Title:
Optimization: Don't prune events on every get
Status in Keystone:
Fix Released
Status in Keystone kilo series:
In Progress
Status in Keystone liberty series:
Fix Released
Bug description:
_prune_expired_events_and_get always locks the backend. Store the time
of the oldest event so that the prune process can be skipped if none
of the events have timed out.
(decided at keystone midcycle - 2015/07/17) -- MorganFainberg
The easiest solution is to do the prune on issuance of new revocation event instead on the get.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1287757/+subscriptions
References