[
https://issues.apache.org/jira/browse/CASSANDRA-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119670#comment-14119670
]
Ananthkumar K S commented on CASSANDRA-7861:
--------------------------------------------
[~brandon.williams] There was link problem for 5 mins to be precise. But the
link was up after that. If cassandra is trying to gossip post that, why does it
have a TCP level problem ?
If the problem is with the network, i would not be able to log into the server
right?I logged into the server in first place from a remote place(not from
within datacenter). So the server is reachable .
If network was the problem, how does it get resolved on restart?
> Node is not able to gossip
> --------------------------
>
> Key: CASSANDRA-7861
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7861
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ananthkumar K S
> Fix For: 2.0.3
>
> Attachments: thread-dump.txt
>
>
> The node is running on xxx.xxx.xxx.xxx. All of a sudden, it was not able to
> gossip and find the other nodes between data centres. We had two nodes
> indicated as down in DC1 but those two nodes were up and running in DC2. When
> we check the two nodes status in DC2, all the nodes in DC1 are denoted as DN
> and the other node in DC2 is denoted as down.
> There seems to be a disconnect between the nodes. I have attached the thread
> dump of the node that was down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
