Hi,
We guess the issue we are facing is related to
https://issues.apache.org/jira/browse/CASSANDRA-9630.
Will it be fixed in 3.11 release.
Thanks and Regards
A.SathishKumar
On Fri, Dec 22, 2017 at 6:15 PM, sat wrote:
> Hi,
>
> We tried rebooting again Node 1 and this time we observed nodeto
Hi,
We tried rebooting again Node 1 and this time we observed nodetool status
displaying "UN" for all 3 nodes in node1.
Executing nodetool status on "Node 3" displays "UN" for all the nodes.
Executing nodetool status on "Node 2" displays "DN" for node 1 (rebooted
node) and "UN" for other 2 node
Hi,
We checked and we were able to telnet to port 7000.
Thanks and Regards
A.SathishKumar
On Fri, Dec 22, 2017 at 3:43 PM, Nitan Kainth wrote:
> Try telnet on your listen port. It must be network issue due to port or
> firewall issue.
>
> Sent from my iPhone
>
> On Dec 22, 2017, at 5:28 PM, sa
Try telnet on your listen port. It must be network issue due to port or
firewall issue.
Sent from my iPhone
> On Dec 22, 2017, at 5:28 PM, sat wrote:
>
>
>
> Hi,
>
> We have 3 nodes in cluster, we rebooted one of the cassandra VM, we noticed
> nodetool status returning "UN" for itself and
Hi,
We have 3 nodes in cluster, we rebooted one of the cassandra VM, we noticed
nodetool status returning "UN" for itself and "DN" for other node, although
we observe gossip sync and ack messages being shared between these nodes.
*Issue in Detail*
*Nodes in cluster*
Node1
Node 2
Node 3
All abov
