yahoo-eng-team team mailing list archive

[Boris Bobrov <bbobrov@xxxxxxxxxxxx>]

Public bug reported:

Keystone becomes extremely slow if one of memcached servers, used as
token persistence driver, stops working. This happens because Keystone
re-initializes memcache client on every call and memcache client loses
information about dead servers and time until they are dead.

To reproduce the issue:
1. Set up two memcached instances on, say, virtual machines
2. Set [token]driver=keystone.token.persistence.backends.memcache_pool.Token
3. Set [memcache]servers=192.168.56.101:11211,192.168.56.102:11211 (change ip to your own)
4. Break down one of the servers. By turning the server off for example
5. Try signing in in Horizon.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1436324

Title:
  Keystone is not HA with memcache as token persistence driver

Status in OpenStack Identity (Keystone):
  New

Bug description:
  Keystone becomes extremely slow if one of memcached servers, used as
  token persistence driver, stops working. This happens because Keystone
  re-initializes memcache client on every call and memcache client loses
  information about dead servers and time until they are dead.

  To reproduce the issue:
  1. Set up two memcached instances on, say, virtual machines
  2. Set [token]driver=keystone.token.persistence.backends.memcache_pool.Token
  3. Set [memcache]servers=192.168.56.101:11211,192.168.56.102:11211 (change ip to your own)
  4. Break down one of the servers. By turning the server off for example
  5. Try signing in in Horizon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1436324/+subscriptions