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 ?

  • Can we rename an output image from “packer build” command over-riding the image name given in packer.json file during run-time?
  • Docker build image 1GB or too big
  • Unable to access Container url in Bluemix for Spring Boot Application
  • If images in Docker are untagged, are they used at all or just orphans?
  • Is it possible for a the host to authenticate to a KDC running on a Docker container?
  • Docker file to call PS1 file with parameters
  • Thanks 🙂

  • Oracle Instant Client - with Docker and PHP
  • Docker usage in compose/swarm mode
  • Docker not allowing push to repo
  • How to identify whether my container is running on AWS ECS or not?
  • Why would I want to to use VOLUME inside a Dockerfile?
  • Docker containers seem to 'inherit' the instance profile of the host ec2. How?
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.