Hi, I am getting following output on problematic node where as no output on working node.
cassandra@cqlsh> select peer, host_id, release_version from system.peers where release_version < '3.0.0' allow filtering; peer | host_id | release_version --------------+--------------------------------------+----------------- 10.39.36.152 | b2d1191e-fdd0-492d-b31f-083fb7109909 | 2.2.5 Regards, Srinivas P From: Bowen Song <[email protected]> Date: Thursday, 29 July 2021 at 2:20 PM To: [email protected] <[email protected]> Subject: Re: Issue with native protocol Can you please run the following query on the problematic node? select peer, host_id, release_version from system.peers where release_version < '3.0.0' allow filtering; I suspect you have a "ghost" 2.x node in the system.peers table on this problematic node. The "ghost" node will not show up in the "nodetool status" output, because it does not exist except in the system.peers table. On 29/07/2021 05:22, Srinivas Polamarasetty wrote: We have tried restarting couple of times and issue remains same so repointed to another node and able to communicate with db. We think some issue with this particular node only Regards, Srinivas Get Outlook for Android<https://urldefense.com/v3/__https:/aka.ms/AAb9ysg__;!!OA8L0MA-!tvax1pa8mcIJHgM6BT88h2DcfNJGXmR6RrRtowKRUm3nUD27sPhZSCejunKF6FHSAOkyFEUdLw$> ________________________________ From: manish khandelwal <[email protected]><mailto:[email protected]> Sent: Thursday, July 29, 2021 8:31:17 AM To: [email protected]<mailto:[email protected]> <[email protected]><mailto:[email protected]> 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 <[email protected]<mailto:[email protected]>> wrote: Query shows 4 but App team also getting below error. They were not able to communicate with this node. com.datastax.driver.core.exceptions.CodecNotFoundException: Codec not found for requested operation: ['org.apache.cassandra.db.marshal.ShortType' <-> java.lang.Short] [2021-07-09 23:26:52.382 -0700] <cluster1-nio-worker-1> com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol version error from /<ip>:<port> for version V4 server supports version V3 [2021-07-09 23:26:52.382 -0700] <cluster1-nio-worker-1> com.datastax.driver.core.Connection - DEBUG: Connection[//<ip>:<port> -1, inFlight=0, closed=true] closing connection [2021-07-09 23:26:52.382 -0700] <cluster1-nio-worker-1> com.datastax.driver.core.Host.STATES - DEBUG: [//<ip>:<port>] Connection[/10.39.38.166:9042-1, inFlight=0, closed=true] closed, remaining = 0 [2021-07-09 23:26:52.383 -0700] <main> com.datastax.driver.core.Cluster - DEBUG: Cannot connect with protocol V4, trying V3 Regards, Srinivas P From: Erick Ramirez <[email protected]<mailto:[email protected]>> Date: Wednesday, 28 July 2021 at 12:39 PM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> 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 to run `SELECT native_protocol_version FROM system.local`? It should come back with 4. Cheers!
