Re: Aws instance stop and star with ebs

10 minutes is 600 seconds, and there are several timeouts that are set to that, including the data center timeout as I recall. You may be forced to tcpdump the interface(s) to see where the chatter is. Out of curiosity, when you restart the node, have you snapped the jvm's memory to see if e.g.

Re: Aws instance stop and star with ebs

Thanks Ben, Before stoping the ec2 I did run nodetool drain .so i ruled it out and system.log also doesn't show commitlogs being applied. On Tue, Nov 5, 2019, 7:51 PM Ben Slater wrote: > The logs between first start and handshaking should give you a clue but my > first guess would be

Re: Aws instance stop and star with ebs

The logs between first start and handshaking should give you a clue but my first guess would be replaying commit logs. Cheers Ben --- *Ben Slater**Chief Product Officer*

Re: Aws instance stop and star with ebs

I can reproduce the issue. I did drain Cassandra node then stop and started Cassandra instance . Cassandra instance comes up but other nodes will be in DN state around 10 minutes. I don't see error in the systemlog DN xx.xx.xx.59 420.85 MiB 256 48.2% id 2 UN