Ask Your Question

A massive 35GB keystone/token.ibd, what happened?

asked 2015-04-06 08:43:01 -0600

gnychis gravatar image

updated 2015-04-06 08:53:23 -0600

All of a sudden I found out that my OpenStack server hit a file size limit. I immediately thought it had something to do with glance and my images, but upon inspection I found that a keystone/token.ibd file grew to 32GB!

$ sudo ls -ltrh ./var/lib/mysql/keystone/token.ibd
-rw-rw---- 1 mysql mysql 34G Apr  5 15:48 ./var/lib/mysql/keystone/token.ibd

This looks to be the keystone database. Does anyone know what could have caused it to grow to this size, how I can prevent this, and how I can potentially fix it? I haven't been able to find anyone with such an issue.

Edit: This might be the issue?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2015-04-06 09:42:29 -0600

Yup looks like you just answered your own question.

cron it and forget about it.

edit flag offensive delete link more

answered 2015-04-06 14:51:04 -0600

You should probably not store tokens in the DB. There is no reason to store tokens in the DB. This is not a scalable solution for production deployments. Have keystone use memcache to store its tokens.

The configuration change to make this happen is simple. In keystone.conf:

driver = keystone.token.backends.memcache.Token

Restart keystone server.

You wont have to worry about the DB anymore.

edit flag offensive delete link more


Great, i will do this!

gnychis gravatar imagegnychis ( 2015-04-06 21:53:55 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-04-06 08:43:01 -0600

Seen: 1,487 times

Last updated: Apr 06 '15