Reduce the severity of being unable to connect to a master gossip port

10/12/27 18:31:30 ERROR distributed.GossipMulticast: IOException when gossiping with 10/12/27 18:31:30 ERROR distributed.GossipMulticast: IOException when gossiping with 0.0.0.0:57890
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.<init>(Socket.java:375)
at java.net.Socket.<init>(Socket.java:189)
at com.cloudera.distributed.GossipMulticast$GossipThread.run(GossipMulticast.java:307)
on xxxx.com
3:34 PMHsieh, Jonathan
you probaly took down a master.
masters use a gossip algorithm to distribute data that doesn't have to be consistent.
if you take a master down, one of the other masters may fail when i tries to gossip info around.