Its worth checking your connectivity on each node to see if the connections
are established:
For example:
# netstat -ant | awk 'NR==2;/7001/'
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp0 0 172.31.10.93:7001 0.0.0.0:* LISTEN
tcp
In the logs nothing strange but “nodetool gossipinfo” seems OK
./nodetool gossipinfo
/192.168.1.10
generation:1453316804
heartbeat:206518
STATUS:18:NORMAL,-1003341236369672970
LOAD:206420:4.3533596E7
SCHEMA:14:6f97097b-45ce-3479-8b2f-af2fef4967e7
DC:8:DC2
RACK:10:rack1
RELEASE_VER
Hi,
do you see any message related to gossip info?
2016-01-21 14:09 GMT+01:00 Bernardino Mota <
bernardino.m...@knowledgeworks.pt>:
> Using Cassandra 2.2.4 on Ubuntu.
>
> We have a cluster with two nodes that during several hours failed to
> connect with each other due to network problems. The d
Using Cassandra 2.2.4 on Ubuntu.
We have a cluster with two nodes that during several hours failed to connect
with each other due to network problems. The database continued to be used in
one of the nodes with writes being stored in the Hints file as supposed.
But now that the network is OK aga
