Keystone is slow and unreliable on big clusters
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Invalid
|
Critical
|
MOS Keystone |
Bug Description
Steps to reproduce:
Deploy 9.0 environment with 3 controllers and large (>50) number of compute nodes
9.0 ISO #121
Start 100 vms (micro flavor) simultaneously using Horizon
Expected results:
All vms are in Active state
Actual result:
Keystone works extremely slow and sometimes doesn't answer at all, many vms are in ERROR state.
The following errors can be found in Apache logs:
Timeout when reading response headers from daemon process 'keystone_main': /usr/lib/
Resource temporarily unavailable: [client 192.168.0.2:42830] mod_wsgi (pid=10571): Unable to connect to WSGI daemon process 'keystone_main' on '/var/run/
Changed in mos: | |
status: | New → Confirmed |
tags: | added: area-keystone keystone |
tags: | added: scale |
Changed in mos: | |
importance: | High → Critical |
Changed in mos: | |
assignee: | Denis Egorenko (degorenko) → MOS Keystone (mos-keystone) |
Suggestions:
- in keystone.conf set revoke_by_id=False
- boost number of workers in the apache config several times
- boost trhead number in memcached config (looks most promising)