Re: Issue with native protocol

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 V3

Re: Issue with native protocol

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, 5/v5

Re: Issue with native protocol

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 lis

Re: Issue with native protocol

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 From: manish khande

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> wrote: > Query shows 4 but App team also getting below error. They were not abl

Re: High memory usage during nodetool repair

Based on the symptoms you described, it's most likely caused by SSTables being mmap()ed as part of the repairs. Set `disk_access_mode: mmap_index_only` so only index files get mapped and not the data files. I've explained it in a bit more detail in this article -- https://community.datastax.com/qu

Re: [RELEASE] Apache Cassandra 4.0.0 released

If you're running Cassandra 3.x, the only data file requirement is that all SSTables present on your cluster are 3.x-era SSTables. This means that you should/should have run upgradesstables at least once on Cassandra 3.x after upgrading from an earlier release before upgrading to Cassandra 4.0.

Re: [RELEASE] Apache Cassandra 4.0.0 released

Thanks Brandon! Anyone know the upgrade path from 3.x? https://cassandra.apache.org/doc/latest/cassandra/getting_started/installing.html Doesn't look like it has specific upgrade instructions. For instance do we need to run nodetool upgradesstables? TIA On 2021/07/26 20:03:59, Brandon Wil

[RELEASE] Apache Cassandra 3.11.11 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.11.11. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

sstable-to-arrow

Hi folks, There was some discussion on here a couple of weeks ago about using the Apache Arrow in memory format for Cassandra data so I thought I'd share the following posts / code we just released as alpha (apache 2 license). Code: https://github.com/datastax/sstable-to-arrow Post Part 1: http

[RELEASE] Apache Cassandra 3.0.25 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.25. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

Re: cassandra 4.0 java 11 support

Anecdotally, I have no issues to report running Cassandra 4.0 on JDK11 and would be supportive of removing the "experimental" classification in an upcoming release. From: Erick Ramirez Sent: Tuesday, July 27, 2021 3:57 PM To: user@cassandra.apache.org Su

Re: High memory usage during nodetool repair

Could it be related to https://issues.apache.org/jira/browse/CASSANDRA-14096 ? On 28/07/2021 13:55, Amandeep Srivastava wrote: Hi team, My Cluster configs: DC1 - 9 nodes, DC2 - 4 nodes Node configs: 12 core x 96GB ram x 1 TB HDD Repair params: -full -pr -local Cassandra version: 3.11.4 I'm ru

High memory usage during nodetool repair

Hi team, My Cluster configs: DC1 - 9 nodes, DC2 - 4 nodes Node configs: 12 core x 96GB ram x 1 TB HDD Repair params: -full -pr -local Cassandra version: 3.11.4 I'm running a full repair on DC2 nodes - one node and one keyspace at a time. During the repair, ram usage on all 4 nodes spike up to 95%

Re: Issue with native protocol

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.3

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!