From b2da4ea131da5e801c860194845acecb4ef6d808 Mon Sep 17 00:00:00 2001 From: Wu Wenxiang Date: Sun, 9 Jun 2013 12:17:34 +0800 Subject: Using sql as default driver for tokens kvs driver for tokens is not a production quality storage method. The shortcomings of using kvs as storage driver for tokens: 1. It requires load balancer to persist connections to a single keystone server by token. 2. The memory will grow out of control until token_flush is run. 3. At some point kvs lookups get very slow because there are millions of keys in the dict. 4. Process restart invalidates all tokens. Fixes: bug #1188370 Change-Id: Ic726e12d798b843412158a7b92f5e3e3a654811f --- etc/keystone.conf.sample | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'etc') diff --git a/etc/keystone.conf.sample b/etc/keystone.conf.sample index f65eab5b..08154124 100644 --- a/etc/keystone.conf.sample +++ b/etc/keystone.conf.sample @@ -119,7 +119,7 @@ # template_file = default_catalog.templates [token] -# driver = keystone.token.backends.kvs.Token +# driver = keystone.token.backends.sql.Token # Amount of time a token should remain valid (in seconds) # expiration = 86400 -- cgit