Re: Discrepancy in nodetool status

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

Re: run cleanup and rebuild simultaneously

Thanks Jeff -- Original -- From: Jeff Jirsa Date: ,12?? 23,2017 09:28 To: user Subject: Re: run cleanup and rebuild simultaneously Should be fine, though it will increase disk usage in dc1 for a while - a

Re: run cleanup and rebuild simultaneously

Should be fine, though it will increase disk usage in dc1 for a while - a reference to the the cleaned up sstables will be held by the rebuild streams, causing you to temporarily increase disk usage until rebuild finishes streaming -- Jeff Jirsa > On Dec 22, 2017, at 4:30 PM, Peng Xiao

Re: Discrepancy in nodetool status

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

run cleanup and rebuild simultaneously

Hi there,Can we run nodetool cleanup in DC1,and run rebuild in DC2 against DC1 simultaneously? in C* 2.1.18 Thanks, Peng Xiao

Re: Discrepancy in nodetool status

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

Discrepancy in nodetool status

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

Re: Cassandra takes more time to join the cluster

Hi Jeff, Thanks for your prompt response. Please find logs. Does Gossip has dependency with NTP, because we find the node we reboot takes time to sync with NTP. When will FailureDetector message kick in, we have this issue only when we see Gossiper and Failure Detector log message. TRACE

Re: Current state of Cassandra on Windows and switching from Windows to Linux

Inline -- Jeff Jirsa > On Dec 22, 2017, at 2:01 AM, Vincent Smit wrote: > > Hi, > > I am currently involved in a project to scale-up an existing Windows > Cassandra cluster because we are planning to migrate large amounts of > historic data. However, I am a bit

Current state of Cassandra on Windows and switching from Windows to Linux

Hi, I am currently involved in a project to scale-up an existing Windows Cassandra cluster because we are planning to migrate large amounts of historic data. However, I am a bit skeptical to keep using Windows for the nodes. I have done some research about Cassandra on Windows and found some