nodetool repair -pr
> > simultaneously on each node, besides the cpu and mem overload?
> > Also if someone can clarify about the safety of an incremental
> > repair.
> >
> > thanks,
> > nuno
> > From: Carlos Rolo
> > Sent: Friday, April 20, 2018
> *From:* Carlos Rolo
> *Sent:* Friday, April 20, 2018 4:55:21 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: cassandra repair takes ages
>
> Changing the datadrives to SSD would help to speed up the repairs.
>
> Also don't run 3
: Friday, April 20, 2018 4:55:21 PM
To: user@cassandra.apache.org
Subject: Re: cassandra repair takes ages
Changing the datadrives to SSD would help to speed up the repairs.
Also don't run 3 node, RF2. That makes Quorum = All.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Cert
Changing the datadrives to SSD would help to speed up the repairs.
Also don't run 3 node, RF2. That makes Quorum = All.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Love your data
rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Li
Hello,
I have a 3 node cluster with RF 2 and using STCS. I use SSDs for commitlogs and
HDDs for data. Apache Cassandra version is 3.11.2.
I basically have a huge keyspace ('newts' from opennms) and a big keyspace
('opspanel'). Here's a summary of the 'du' output for one node (which is more
or l
