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 ?

  • Docker access localhost
  • Is there a clever way to do this with Docker (maybe via save/load/diff)?
  • Effect of a driver in the host OS to a Docker process
  • how to create images interactive from Dockerfile? [duplicate]
  • How to push container to Google Container Registry (unable to create repository)
  • How to change container configuration without Dockerfile?
  • Thanks 🙂

  • Golang: Preview of managed VM app returns error
  • Google Cloud Shell, Upgrade Docker from 1.9.1, it's impossible?
  • Docker restart entrypoint
  • Restart one service in docker swarm stack
  • Docker MYSQL '[2002] Connection refused'
  • Dockerfiles to run AEM subsystems in containers
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.