Keystone is not HA with memcache as token persistence driver
Bug #1436324 reported by
Boris Bobrov
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Won't Fix
|
Low
|
Unassigned |
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]
3. Set [memcache]
4. Break down one of the servers. By turning the server off for example
5. Try signing in in Horizon.
tags: | added: kilo-rc-potential |
Changed in keystone: | |
importance: | Undecided → Medium |
tags: | removed: kilo-rc-potential |
Changed in keystone: | |
assignee: | Boris Bobrov (bbobrov) → nobody |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/167594
Review: https:/