Re: Issue with native protocol

[Srinivas Polamarasetty]

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 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 Srinivas Polamarasetty 
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]  
com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol version 
error from /: for version V4 server supports version V3

[2021-07-09 23:26:52.382 -0700]  
com.datastax.driver.core.Connection - DEBUG: Connection[//: -1, 
inFlight=0, closed=true] closing connection

[2021-07-09 23:26:52.382 -0700]  
com.datastax.driver.core.Host.STATES - DEBUG: [//:] 
Connection[/10.39.38.166:9042-1, inFlight=0, closed=true] closed, remaining = 0

[2021-07-09 23:26:52.383 -0700]  com.datastax.driver.core.Cluster - 
DEBUG: Cannot connect with protocol V4, trying V3









Regards,

Srinivas P





From: Erick Ramirez 
mailto:erick.rami...@datastax.com>>
Date: Wednesday, 28 July 2021 at 12:39 PM
To: 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!

Re: Issue with native protocol

[manish khandelwal]

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 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] 
> com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol
> version error from /: for version V4 server supports version V3
>
> [2021-07-09 23:26:52.382 -0700] 
> com.datastax.driver.core.Connection - DEBUG: Connection[//: -1,
> inFlight=0, closed=true] closing connection
>
> [2021-07-09 23:26:52.382 -0700] 
> com.datastax.driver.core.Host.STATES - DEBUG: [//:]
> Connection[/10.39.38.166:9042-1, inFlight=0, closed=true] closed,
> remaining = 0
>
> [2021-07-09 23:26:52.383 -0700]  com.datastax.driver.core.Cluster -
> 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 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!
>

Re: High memory usage during nodetool repair

[Erick Ramirez]

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/questions/6947/. Cheers!

>

Re: [RELEASE] Apache Cassandra 4.0.0 released

[Scott Andreas]

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. This is necessary because Cassandra 4.0 cannot read the legacy 
Cassandra 2.x SSTable format.

In the same vein, it's not necessary to run upgradesstables after upgrading 
from Cassandra 3.x to Cassandra 4.0 as 4.0 is able to read 3.x's data format 
fine. At a later time in the future, it may be necessary to run upgradesstables 
prior to upgrading to confirm there are no 3.x SSTables left -- but no such 
post-4.0 SSTable format changes have been proposed yet.


From: Adam Scott 
Sent: Wednesday, July 28, 2021 2:58 PM
To: user@cassandra.apache.org
Subject: 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 Williams  wrote:
> The Cassandra team is pleased to announce the release of Apache
> Cassandra version 4.0.0.
>
> 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 and binary distributions are available in our
> download section:
>
> http://cassandra.apache.org/download/
>
> This version is the initial release in the 4.0 series. As always,
> please pay attention to the release notes[2] and Let us know[3] if you
> were to encounter any problem.
>
> Enjoy!
>
> [1]: CHANGES.txt
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.0
> [2]: NEWS.txt 
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.0
> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>

Re: [RELEASE] Apache Cassandra 4.0.0 released

[Adam Scott]

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 Williams  wrote: 
> The Cassandra team is pleased to announce the release of Apache
> Cassandra version 4.0.0.
> 
> 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 and binary distributions are available in our
> download section:
> 
> http://cassandra.apache.org/download/
> 
> This version is the initial release in the 4.0 series. As always,
> please pay attention to the release notes[2] and Let us know[3] if you
> were to encounter any problem.
> 
> Enjoy!
> 
> [1]: CHANGES.txt
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.0
> [2]: NEWS.txt 
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.0
> [3]: https://issues.apache.org/jira/browse/CASSANDRA
> 

[RELEASE] Apache Cassandra 3.11.11 released

[Brandon Williams]

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 and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always,
please pay attention to the release notes[2] and let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.11
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.11
[3]: https://issues.apache.org/jira/browse/CASSANDRA

sstable-to-arrow

[Sebastian Estevez]

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:
https://www.datastax.com/blog/analyzing-cassandra-data-using-gpus-part-1
Post Part 2:
https://www.datastax.com/blog/analyzing-cassandra-data-using-gpus-part-2

I also think the cross language sstable parsing code and visual
documentation is a tremendous contribution for the project and would love
to see more folks pick it up and use it for other purposes.

If anyone is interested feel free to reach out or join our live workshop on
this topic in mid August:

https://www.eventbrite.com/e/workshop-analyzing-cassandra-data-with-gpus-tickets-164294668777

--Seb

[RELEASE] Apache Cassandra 3.0.25 released

[Brandon Williams]

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 and binary distributions are listed in our download section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.25
[2]: NEWS.txt 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.25
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: cassandra 4.0 java 11 support

[Scott Andreas]

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
Subject: Re: cassandra 4.0 java 11 support

There's been some discussion around removing the "experimental" tag for C* 4.0 
+ Java 11 so by all means, we encourage everyone to try it and report back to 
the community if you run into issues. Java 11 support was added 2 years ago so 
I think most of the issues have been ironed out. Now that 4.0 is out, we're 
hoping there would be more users testing it out. Cheers!

Re: High memory usage during nodetool repair

[Bowen Song]

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 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%. 
Have tried setting xmx to 24GB, 31GB, 32GB, and 64GB but all show the 
same behavior. Could you please advise what might be consuming such 
high levels of off-heap memory and what can be done to cap/limit its use?


We run no other process apart from Cassandra daemon on these nodes.

Regards,
Aman

High memory usage during nodetool repair

[Amandeep Srivastava]

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%. Have
tried setting xmx to 24GB, 31GB, 32GB, and 64GB but all show the same
behavior. Could you please advise what might be consuming such high levels
of off-heap memory and what can be done to cap/limit its use?

We run no other process apart from Cassandra daemon on these nodes.

Regards,
Aman

Re: Issue with native protocol

[Srinivas Polamarasetty]

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]  
com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol version 
error from /: for version V4 server supports version V3
[2021-07-09 23:26:52.382 -0700]  
com.datastax.driver.core.Connection - DEBUG: Connection[//: -1, 
inFlight=0, closed=true] closing connection
[2021-07-09 23:26:52.382 -0700]  
com.datastax.driver.core.Host.STATES - DEBUG: [//:] 
Connection[/10.39.38.166:9042-1, inFlight=0, closed=true] closed, remaining = 0
[2021-07-09 23:26:52.383 -0700]  com.datastax.driver.core.Cluster - 
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 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!

Re: Issue with native protocol

[Erick Ramirez]

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!

Issue with native protocol

[Srinivas Polamarasetty]

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 social-graph-cassandra-cluster at :.

[cqlsh 5.0.1 | Cassandra 3.11.5 | CQL spec 3.4.4 | Native protocol v3]

Use HELP for help.

cassandra@cqlsh>


Connected to social-graph-cassandra-cluster at :.

[cqlsh 5.0.1 | Cassandra 3.11.5 | CQL spec 3.4.4 | Native protocol v4]

Use HELP for help.

Kindly let us know the fix for the same.


Regards,
Srinivas P