MessageListenerContainer not listening after crashing master redis instance in redis sentinel in docker env

I have a question.
I have redis sentinel setup in the docker env. (without docker, things work fine)
I am using the Jedis and redis sentinel support from spring.
RedisMessageListenerContainer is supposed to take care the subscriber part.
However, after shutting down the redis master node, I am able to output the new ip and port from connection factory … (i.e., the ip and port is referring to the new master).

But … very often … All the subscribers become not listening anymore.
Does anyone encounter this issue in docker ?

  • how get env variables from docker in symfony yml config file
  • Putting a uWSGI fast router in front of uWSGI servers running in docker containers
  • Enable Postgis extension Postgres in Dockerfile
  • why doesn't chown work in Dockerfile?
  • docker exec with find -exec option (find: missing argument to `-exec')
  • Ubuntu on Managed VMs using custom runtime
  • Thanks 🙂

  • Error while execing a docker image
  • Running a subset of docker commands without sudo
  • Identical dockerfiles giving different behaviours
  • Where to find more explicit errors given container error status codes?
  • Can I run a docker container with an own, externally and host accessible, IP address on a Mac
  • What is the need of images in docker
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.