This patch expose a couple of pymemcache's HashClient public
params that can be useful to configure HA and failover for
clustered memcached servers.
These options can be used in addition of the previously added
retrying mechanismes.
This patch rely on recent changes [1] of dogpile.cache that
aim to expose these options too.
This patch is needed to fix a TLS issue on stable branches introduced by
pymemcache (since train), where if a cluster node disappear the client
will fail without retrying to reconnect or to switch to an other node of
the cluster.
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.cache/ +/826594 /opendev. org/openstack/ oslo.cache/ commit/ 55cb199f90b27ce f203bca8edb9431 f9d7ed841c
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/xena
commit 55cb199f90b27ce f203bca8edb9431 f9d7ed841c
Author: Hervé Beraud <email address hidden>
Date: Mon Jan 17 14:59:25 2022 +0100
Expose pymemcache's HashClient public params
This patch expose a couple of pymemcache's HashClient public
params that can be useful to configure HA and failover for
clustered memcached servers.
These options can be used in addition of the previously added
retrying mechanismes.
This patch rely on recent changes [1] of dogpile.cache that
aim to expose these options too.
This patch is needed to fix a TLS issue on stable branches introduced by
pymemcache (since train), where if a cluster node disappear the client
will fail without retrying to reconnect or to switch to an other node of
the cluster.
[1] https:/ /gerrit. sqlalchemy. org/c/sqlalchem y/dogpile. cache/+ /3528
Partial-Bug: #1959562 /review. opendev. org/c/openstack /requirements/ +/826995 08b87871ddff1b3 ced27cc7fce f23831d7445f6b3 3c866cd0c6)
Depends-On: https:/
Change-Id: I24fc853db4237c
(cherry picked from commit cb118d04cea318d