cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7861) Node is not able to gossip
Date Wed, 24 Sep 2014 16:32:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146492#comment-14146492
] 

Shawn Kumar commented on CASSANDRA-7861:
----------------------------------------

I was unable to reproduce this. I first brought up a cluster, ran stress as a workload and
then forced a network partition. After healing the partition I didn't notice this problem.
If you have any further information that could help us reproduce this, feel free to reopen
the ticket.

> 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
>              Labels: qa-resolved
>             Fix For: 2.0.3
>
>
> 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)

Mime
View raw message