** Also affects: keystone/kilo Importance: Undecided Status: New ** Also affects: keystone/liberty Importance: High Assignee: Morgan Fainberg (mdrnstm) Status: In Progress
** Changed in: keystone/kilo Status: New => Triaged ** Changed in: keystone/kilo Importance: Undecided => High ** Changed in: keystone/kilo Assignee: (unassigned) => Morgan Fainberg (mdrnstm) -- 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: In Progress Status in Keystone kilo series: Triaged Status in Keystone liberty series: In Progress 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp