Horizon require memcached to flush data on upgrade
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
New
|
Undecided
|
Gaël THEROND | ||
Bug Description
From time to time when performing an upgrade you can end up with a not working horizon instance due to stale data on memcached.
This result in a constantly rebooting horizon container with the following error:
https:/
As tracked down in here: https:/
The issue is memcached stale data that need to be flushed.
In our context, we can't just restart memcached instance as they kept cache alive even across docker restart.
In order to solve this issue with as less as downtime possible we have two main solutions:
1°/ - We serially flush all deployed memcached instance using the memcached flush_all command feature, however it require netcat or equivalent (nc/socat/etc) to inject the command as follow: echo 'flush_all' > nc <host_api_net> 11211
2°/ - We drop and re-instanciate the memcached container serially during the horizon upgrade task.
What do you prefer?
| Changed in kolla-ansible: | |
| assignee: | nobody → Gaël THEROND (fl1nt) |
| Maksim Malchuk (mmalchuk) wrote | #1 |
just to clarify one of the solution (2): drop and re-instanciate means not simple stop/start docker containers?