Something else we recently read was Django's documentation on memcached at https://docs.djangoproject.com/en/3.1/topics/cache/#memcached.
The document describes Django taking advantage of multiple memcached backends when they are provided in a comma-separated list.
After reading this we decided to trial reverting https://docs.openstack.org/openstack-ansible-memcached_server/ussuri/configure-ha.html entirely - all services are now talking to memcached directly.
We've also been having issues with Horizon frequently logging users out - often within 5 minutes of logging in - and since reverting the HA memcached settings users are no longer being incorrectly logged out. So that's promising!
Something else we recently read was Django's documentation on memcached at https:/ /docs.djangopro ject.com/ en/3.1/ topics/ cache/# memcached.
The document describes Django taking advantage of multiple memcached backends when they are provided in a comma-separated list.
After reading this we decided to trial reverting https:/ /docs.openstack .org/openstack- ansible- memcached_ server/ ussuri/ configure- ha.html entirely - all services are now talking to memcached directly.
We've also been having issues with Horizon frequently logging users out - often within 5 minutes of logging in - and since reverting the HA memcached settings users are no longer being incorrectly logged out. So that's promising!