I have been experiencing an issue where kombu-sentinel support is leaking the socket opened to redis-sentinel nodes.
Kombu-sentinel keeps reconnecting the redis sentinel nodes and leaving the connected sockets behind, If there is network glitch or some other known-unknown issue which is preventing kombu-sentinel to connect to redis master node
Reproduction: when celery is configured with different "mastername" in comparison to what redis-sentinel setups are configured with.
For ex: Redis sentinel setup has master as "masternode" but the celery broker is configured as "masternode1". This way kombu-sentinel support will not be able to find the redis master node and keep reconnecting and leaving the connected sentinel sockets behind.
Redis sentinel will reach to "max connected client" eventually and the complete system will be dead.
I have been experiencing an issue where kombu-sentinel support is leaking the socket opened to redis-sentinel nodes. Kombu-sentinel keeps reconnecting the redis sentinel nodes and leaving the connected sockets behind, If there is network glitch or some other known-unknown issue which is preventing kombu-sentinel to connect to redis master node
Reproduction: when celery is configured with different "mastername" in comparison to what redis-sentinel setups are configured with.
For ex: Redis sentinel setup has master as "masternode" but the celery broker is configured as "masternode1". This way kombu-sentinel support will not be able to find the redis master node and keep reconnecting and leaving the connected sentinel sockets behind.
Redis sentinel will reach to "max connected client" eventually and the complete system will be dead.