Then that's the cause for the node negotiating down to an older protocol
version by design for dealing with mixed-version clusters as Sam described
in his response. As Bowen stated, you must have had an old node back from
when it was still a C* 2.2 cluster that you probably tried to
We don’t see this node as part of our cluster. Not listed in nodetool status as
well.
Regards,
Srinivas P
From: Erick Ramirez
Date: Friday, 30 July 2021 at 9:55 AM
To: user@cassandra.apache.org
Subject: Re: Issue with native protocol
Is 10.39.36.152 part of the cluster or is it dead?
Is 10.39.36.152 part of the cluster or is it dead?
>
ersion
--+--+-
10.39.36.152 | b2d1191e-fdd0-492d-b31f-083fb7109909 | 2.2.5
Regards,
Srinivas P
From: Bowen Song
Date: Thursday, 29 July 2021 at 2:20 PM
To: user@cassandra.apache.org
Subject: Re: Issue with native protoco
sandra.apache.org
*Subject:* Re: Issue with native protocol
Have you tried restarting your application? It should renegotiate the
protoco during handshake and should resolve the issue.
On Wed, Jul 28, 2021 at 3:06 PM Srinivas Polamarasetty
<mailto:srinivas.polamarase...@logmein.com>&
Assuming that the one node doesn't have
native_transport_max_negotiable_protocol_version=3 in cassandra.yaml, you could
check its log for
"Detected peers which do not fully support protocol V4. Capping max negotiable
version to V3".
The details are in CASSANDRA-15193, but tl;dr is that a
Thanks, Pekka. But we know from an earlier post from Srinivas that the
driver is trying to negotiate with v4 but the node wouldn't:
[2021-07-09 23:26:52.382 -0700]
com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol
version error from /: for version V4 server supports version
Hi,
On Thu, Jul 29, 2021 at 9:44 AM Erick Ramirez
wrote:
> When you restart C*, you should have an entry in the logs which look like
> this that indicates it defaults to v4:
>
> INFO [main] 2021-07-28 20:45:31,178 StorageService.java:650 - Native
> protocol supported versions: 3/v3, 4/v4,
When you restart C*, you should have an entry in the logs which look like
this that indicates it defaults to v4:
INFO [main] 2021-07-28 20:45:31,178 StorageService.java:650 - Native
protocol supported versions: 3/v3, 4/v4, 5/v5-beta (default: 4/v4)
I'm hoping someone else here on the mailing
manish khandelwal
Sent: Thursday, July 29, 2021 8:31:17 AM
To: user@cassandra.apache.org
Subject: Re: Issue with native protocol
Have you tried restarting your application? It should renegotiate the protoco
during handshake and should resolve the issue.
On Wed, Jul 28, 2021 at 3:06 PM Sr
t; DEBUG: Cannot connect with protocol V4, trying V3
>
>
>
>
>
>
>
>
>
> Regards,
>
> Srinivas P
>
>
>
>
>
> *From: *Erick Ramirez
> *Date: *Wednesday, 28 July 2021 at 12:39 PM
> *To: *user@cassandra.apache.org
> *Subject: *Re: Issue with
ivas P
From: Erick Ramirez
Date: Wednesday, 28 July 2021 at 12:39 PM
To: user@cassandra.apache.org
Subject: Re: Issue with native protocol
Someone asked me about the same issue a couple of months ago and we never
managed to figure out why the wrong version is being displayed.
Could you try
Someone asked me about the same issue a couple of months ago and we never
managed to figure out why the wrong version is being displayed.
Could you try to run `SELECT native_protocol_version FROM system.local`? It
should come back with 4. Cheers!
Team,
We are having strange issue with one of Cassandra node in a cluster. All the
nodes were connecting fine with native protocol version v4 but only 1 node is
connecting to v3. Not sure, how can we fix the issue as all the config files
were same across the cluster.
Connected to
14 matches
Mail list logo
