Issue

• The issue happens where one container instances potentially loses connection from the cluster group using fabric server:

20:46:11,275 | INFO  | d-2-SendThread() | ClientCnxn       | 53 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.2.0.redhat-024 | Opening socket connection to server /127.0.0.1:2181
20:46:11,354 | INFO  | (localhost:2181) | ZooKeeperSaslClient    | 53 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.2.0.redhat-024 | Client will not SASL-authenticate because the default JAAS configuration section 'Client' could not be found. If you are not using SASL, you may ignore this. On the other hand, if you expected SASL to work, please fix your JAAS configuration.
20:46:11,358 | WARN  | (localhost:2181) | ClientCnxn      | 53 - org.fusesource.fabric.fabric-linkedin-zookeeper - 7.2.0.redhat-024 | Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)[:1.7.0_45]
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:735)[:1.7.0_45]
        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)[53:org.fusesource.fabric.fabric-linkedin-zookeeper:7.2.0.redhat-024]
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1035)[53:org.fusesource.fabric.fabric-linkedin-zook