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 ?

  • What is the interaction of Docker's CpuShares between containers?
  • Deploy web app in docker data container vs volume
  • De-allocating memory after python tensorflow workbook execution
  • Choose available memory for containers in Rancher
  • Custom MongoDb docker image
  • docker --storage-opt dm.basesize=40G does not work?
  • Thanks 🙂

  • Docker - How to update images
  • Change process limit of open file descriptors inside a container [duplicate]
  • Unable to create docker virtual machine
  • why did the pulling process in docker act like this?
  • Issues when starting docker build on windows
  • xhost command for docker GUI apps (Eclipse)
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.