> TRACE 14:42:06,248 unable to connect to /10.33.3.20 > java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method)
So that's interesting since it is a clear failure that comes from the operating system and indicates something which can be observed outside of cassandra using system tools. Presumably either cassandra is somehow connecting to the wrong port, or this is a firewalling/os/network issue, or the 'other' cassandra is not listening on the port. Using tcpdump/netstat -nlp should narrow that down. Is it possible connections only succeed in one direction for example? -- / Peter Schuller
