On 01/28/2015 01:13 AM, Fischer, Matt wrote:
Our keystone database is clustered across regions, so we have this job
running on node1 in each site on alternating hours. I don’t think you’d
want a bunch of cron jobs firing off all at once to cleanup tokens on
multiple clustered nodes. That’s
(not for usage questions);
openstack-operat...@lists.openstack.org
*Subject:* Re: [Openstack-operators]
[openstack-dev][openstack-operators]flush expired tokens and moves deleted
instance
It is still mentioned in the Juno installation docs:
By default, the Identity service stores expired tokens
] [openstack-dev][openstack-operators]flush
expired tokens and moves deleted instance
It is still mentioned in the Juno installation docs:
By default, the Identity service stores expired tokens in the database
indefinitely. The
accumulation of expired tokens considerably increases the database size
It is still mentioned in the Juno installation docs:
By default, the Identity service stores expired tokens in the database
indefinitely. The
accumulation of expired tokens considerably increases the database size and
might degrade
service performance, particularly in environments with limited
