e info varies by the
> OS flavor and version.
>
> But many of the stats are kind of self-explanatory.
>
>
>
> *From: *Jeff Jirsa
> *Date: *Friday, September 29, 2017 at 10:32 AM
> *To: *cassandra
> *Subject: *Re: Issue with New Production Cluster
>
>
>
ailed connections at the cassandra
> layer?
>
>
>
> Thanks
>
> J
>
>
>
> *From:* Jeff Jirsa [mailto:jji...@gmail.com]
> *Sent:* 29 September 2017 16:07
>
> *To:* cassandra
> *Subject:* Re: Issue with New Production Cluster
>
>
>
> The failure detec
017-09-29 15:28:41,394 FailureDetector.java:456 -
> Ignoring interval time of 2087037617 <(208)%20703-7617> for /10.172.181.63
>
> INFO [HANDSHAKE-/10.172.181.61] 2017-09-29 15:28:47,132
> OutboundTcpConnection.java:523 - Handshaking version with /10.172.181.61
>
>
&g
handshake with the nodes??
Any suggestions would be great, I have to go to the Network team with this, but
I’m not sure where to start…
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: 29 September 2017 14:54
To: cassandra
Subject: Re: Issue with New Production Cluster
What version?
If you retry
What version?
If you retry immediately, does it reconnect?
Anything in the logs?
What you describe is atypical - timeouts on queries can (and will) happen
occasionally under load, but timeout on connect is atypical. Any sign of
networking issues/slowness/dns problems/etc?
On Fri, Sep 29, 2017 at
Hi Community,
I have a 6 node ring, covering 2 DC's, the ring isn't being used yet and we are
just in the connectivity and testing phase. So the boxes are NOT under any load.
I've gone to connect to CQLSH this afternoon and I've had this returned:
cqlsh xx.xxx.xxx.xx -u cassandra -p cassandra
C
