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://aka.ms/AAb9ysg> ________________________________ From: manish khandelwal <manishkhandelwa...@gmail.com> Sent: Thursday, July 29, 2021 8:31:17 AM To: user@cassandra.apache.org <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 Srinivas Polamarasetty <srinivas.polamarase...@logmein.com<mailto:srinivas.polamarase...@logmein.com>> 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 <erick.rami...@datastax.com<mailto:erick.rami...@datastax.com>> Date: Wednesday, 28 July 2021 at 12:39 PM To: user@cassandra.apache.org<mailto:user@cassandra.apache.org> <user@cassandra.apache.org<mailto: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 to run `SELECT native_protocol_version FROM system.local`? It should come back with 4. Cheers!