Correct repair job

Hello, I am looking to run 'nodetool repair -pr' for my 30 node Cassandra cluster. My question is, do I need to run that command on every one of the 30 nodes? How about if I have multiple DC's, can a single repair job apply too all nodes/DC's?

Cassandra trace

Hello, Does anyone know how I can see queries coming when they're as prepared statements when trace is turned on Cassandra 3.x? If trace doesn't show, any ideas how I can see these type of queries?

Upgrade to version 3

Hello, If we are upgrading from version 2.2 to 3.x, should we go directly to latest version 3.11.3? Anything we need to look out for? If anyone can point to an upgrade process that would be great!

Re: Large partitions

I disagree. We had several over 150MB in 3.11 and we were able to break cluster doing r/w from these partitions in a short period of time. On Thu, Sep 13, 2018, 12:42 Gedeon Kamga wrote: > Folks, > > Based on the information found here > https://docs.datastax.com/en/dse-planning/doc/planning/pl

Re: Upgrade from 2.1 to 3.11

.11.3 instead which has some memory > leaks fixes. > > > > On Tue, Aug 28, 2018 at 9:59 AM, Mun Dega wrote: > > I am surprised that no one else ran into any issues with this version. GC > can't catch up fast enough and there is constant Full GC taking place. > >

Huge number of Mismatchs in the logs

I upgraded from 2.1 to 3.11 and started to get huge number of Digest mismatch errors in the DEBUG log. I ran a full repair in the cluster but it did not seem to cut back on these. My consistency is QUORUM so my guess is this error is on reads but would this also affect my writes to all replicas i

Re: Upgrade from 2.1 to 3.11

iated. Ma On Fri, Aug 24, 2018, 04:30 Mohamadreza Rostami < mohamadrezarosta...@gmail.com> wrote: > You have very large heap,it’s take most of cpu time in GC stage.you > should in maximum set heap on 12GB and enable row cache to your cluster > become faster. > > On Friday

Re: Upgrade from 2.1 to 3.11

Looks like there are a couple of issues open regarding 3.11.2 release: https://issues.apache.org/jira/browse/CASSANDRA-14355 https://issues.apache.org/jira/browse/CASSANDRA-14495 Ma On Thu, Aug 23, 2018 at 10:54 PM Mun Dega wrote: > Interesting. Any other suggestions what other thi

Re: Upgrade from 2.1 to 3.11

memory issue. > > On Thursday, 23 August 2018, 16:04:20 GMT-7, Mun Dega > wrote: > > > 120G data > 28G heap out of 48 on system > 9 node cluster, RF3 > > > On Thu, Aug 23, 2018, 17:19 Mohamadreza Rostami < > mohamadrezarosta...@gmail.com> wrote: > >

Re: Upgrade from 2.1 to 3.11

120G data 28G heap out of 48 on system 9 node cluster, RF3 On Thu, Aug 23, 2018, 17:19 Mohamadreza Rostami < mohamadrezarosta...@gmail.com> wrote: > Hi, > How much data do you have? How much RAM do your servers have? How much do > you have a heep? > On Thu, Aug 23, 2018 at

Upgrade from 2.1 to 3.11

Hello, We recently upgraded from Cassandra 2.1 to 3.11.2 on one cluster. The process went OK including upgradesstable but we started to experience high latency for r/w, occasional OOM and long GC pause after. For the same cluster with 2.1, we didn't have any issues like this. We also kept serve