Re: Cassandra Repair question

Yes - agree with Sergio. For the majority of use cases, the best practice for repair is to use Cassandra Reaper. > On Oct 19, 2019, at 12:06 am, Sergio wrote: > > Use Cassandra reaper > > On Fri, Oct 18, 2019, 10:12 PM Krish Donald > wrote: > Thanks Manish, > >

Re: Cassandra Repair question

Use Cassandra reaper On Fri, Oct 18, 2019, 10:12 PM Krish Donald wrote: > Thanks Manish, > > What is the best and fastest way to repair a table using nodetool repair ? > We are using 256 vnodes . > > > On Fri, Oct 18, 2019 at 10:05 PM manish khandelwal < > manishkhandelwa...@gmail.com> wrote: >

Re: Cassandra Repair question

Thanks Manish, What is the best and fastest way to repair a table using nodetool repair ? We are using 256 vnodes . On Fri, Oct 18, 2019 at 10:05 PM manish khandelwal < manishkhandelwa...@gmail.com> wrote: > No it will only cover primary ranges of nodes on single rac. Repair with > -pr option i

Re: Cassandra Repair question

No it will only cover primary ranges of nodes on single rac. Repair with -pr option is to be run on all nodes in a rolling manner. Regards Manish On 19 Oct 2019 10:03, "Krish Donald" wrote: > Hi Cassandra experts, > > > We are on Cassandra 3.11.1. > > We have to run repairs for a big cluster. >

Cassandra Repair question

Hi Cassandra experts, We are on Cassandra 3.11.1. We have to run repairs for a big cluster. We have 2 DCs. 3 RACs in each DC. Replication factor is 3 for each datacenter . So if I run repair on all nodes of a single RAC with "pr" option then ideally it will cover all the ranges. Please cor

Query regarding cassandra repair

Hi, Day before yesterday, I had issued a full sequential repair on one of my nodes in a 5 node cassandra cluster for a single table using the below command. nodetool repair -full -seq -tr > Now the node on which the command was issued was repaired properly as can be infered from the below com

Re: Cassandra repair in different version

Is there a reason why these versions are so different ? I would recommend bringing 3.0.6 to 3.0.13 before doing cluster wise commands. Rahul Singh Chief Executive Officer m 202.905.2818 Anant Corporation 1010 Wisconsin Ave NW, Suite 250 Washington, D.C. 20007 We build and manage digital busines

Cassandra repair in different version

Hi , i have 5 node cassandra cluster. 3 nodes are in 3.0.13 version and 2 nodes are in 3.0.6. Is it safe to do a node repair on the cluster?? Regards, Renoy

Re: Cassandra Repair

I would recommend at least looking at reaper before trying to engineer another way. On Jul 17, 2018, 12:56 PM -0400, rajasekhar kommineni , wrote: > nodetool tablestats has an attribute for Percent repaired, can we target the > tables based the % given. > > > > > On Jul 17, 2018, at 4:45 AM, Rah

Re: Cassandra Repair

nodetool tablestats has an attribute for Percent repaired, can we target the tables based the % given. > On Jul 17, 2018, at 4:45 AM, Rahul Singh wrote: > > Have you considered looking into reaper project — could save you time in > figuring out your own strategy. > https://github.com/thelas

Re: Cassandra Repair

Have you considered looking into reaper project — could save you time in figuring out your own strategy.  https://github.com/thelastpickle/cassandra-reaper Otherwise you can always do a round robin of cron jobs per node once a week… Your repair cycle should repair all servers within a window les

Cassandra Repair

Hello All, I have all cluster nodes in Cloud, and there is very rare chance for nodes going down. I want to prepare repair strategy to my cluster, so need inputs on any calculations to decide when to go for repair. Also let me know if my statement is correct or not "It’s not only node down

Re: cassandra repair takes ages

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

Re: cassandra repair takes ages

> *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

Re: cassandra repair takes ages

: 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

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 Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Li

cassandra repair takes ages

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

Re: Cassandra Repair Duration.

It's all here: https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/opsRepairNodesWhen.html -B On Thu, Jan 25, 2018 at 6:08 AM Karthick V wrote: > *You can (and probably should) run repairs as apart of routine >> maintenance.* > > > Can u explain any use case for why do we need th

Re: Cassandra Repair Duration.

> > *You can (and probably should) run repairs as apart of routine > maintenance.* Can u explain any use case for why do we need this? On Wed, Jan 24, 2018 at 5:35 PM, wrote: > Hi Karthick, repairs can be tricky. > > You can (and probably should) run repairs as apart of routine > maintena

RE: Cassandra Repair Duration.

...@gmail.com] Sent: Wednesday, January 24, 2018 1:58 AM To: user@cassandra.apache.org Subject: Re: Cassandra Repair Duration. Periodically I have been running Full repair process befor GC Grace period as mentioned in the best practices.Initially, all went well but as the data size increases Repair

Re: Cassandra Repair Duration.

Hi Karthick, repairs can be tricky. You can (and probably should) run repairs as apart of routine maintenance. And of course absolutely if you lose a node in a bad way. If you decommission a node for example, no “extra” repair needed. If you are using TWCS you should probably not run repai

Re: Cassandra Repair Duration.

Periodically I have been running Full repair process befor GC Grace period as mentioned in the best practices.Initially, all went well but as the data size increases Repair duration has increased drastically and we are also facing Query timeouts during that time and we have tried incremental repair

Cassandra Repair Duration.

Hi,

RE: [EXTERNAL] Re: Cassandra repair process in Low Bandwidth Network

:27 AM To: cassandra Subject: [EXTERNAL] Re: Cassandra repair process in Low Bandwidth Network Hi Kishore, Just to make sure we're all on the same page, I presume you're doing full repairs using something like 'nodetool repair -pr', which repairs all data for a given toke

Re: Cassandra repair process in Low Bandwidth Network

Hi Kishore, Just to make sure we're all on the same page, I presume you're doing full repairs using something like 'nodetool repair -pr', which repairs all data for a given token range across all of your hosts in all of your dcs. Is that a correct assumption to start? In addition to throttling in

Cassandra repair process in Low Bandwidth Network

Hi, we have a cassandra cluster with 7 nodes each in 3 datacenters. We are using C* 2.1.15.4 version. Network bandwidth between DC1 and DC2 is very good (10Gbit/s) and a dedicated one. However network pipe between DC1 and DC3 and between DC2 and DC3 is very poor and has only 100 MBit/s an

Re: Is it a must to run Cassandra repair in scheduled time

ate:* 2016-11-18 18:07 > *To:* user > *Subject:* Re: Is it a must to run Cassandra repair in scheduled time > Hi Simon, > > See http://www.datastax.com/dev/blog/repair-in-cassandra for a good > explanation. Basically repair is not a good word because it suggests it is > fixin

Re: Is it a must to run Cassandra repair in scheduled time

Thanks Ben for the response. It's very helpfull and it's really what I want. From: Ben Dalling Date: 2016-11-18 18:07 To: user Subject: Re: Is it a must to run Cassandra repair in scheduled time Hi Simon, See http://www.datastax.com/dev/blog/repair-in-cassandra for a good e

Re: Is it a must to run Cassandra repair in scheduled time

d repair is an important > thing to do. To avoid trouble in putting Cassandra in production > environment, I have some questions. > 1. What exactly does Cassandra repair do? > 2. I saw someone do repair in scheduled time, daily or weekly. Is it a > must to do this? > 3. In which

Is it a must to run Cassandra repair in scheduled time

Hi All, I'm new to Cassandra and from the mail chain seemed repair is an important thing to do. To avoid trouble in putting Cassandra in production environment, I have some questions. 1. What exactly does Cassandra repair do? 2. I saw someone do repair in scheduled time, daily or weekly. Is

RE: cassandra repair error

] Sent: Thursday, July 16, 2015 8:59 AM To: user@cassandra.apache.org Subject: Re: cassandra repair error Hello, It seems that is a problem with Cassandra trying to delete a directory that is not empty. First time seeing this error. Are your harddrives with enough space and working correctly

Re: cassandra repair error

Hello, It seems that is a problem with Cassandra trying to delete a directory that is not empty. First time seeing this error. Are your harddrives with enough space and working correctly? Regards, Carlos Juzarte Rolo Cassandra Consultant Pythian - Love your data rolo@pythian | Twitter: cjrolo

cassandra repair error

Hi, We're using Cassandra 2.0.10 ( 2 DC, 3 Nodes each RF=3 for each DC). During one of the weekly repairs, we received the following error: ERROR [ValidationExecutor:1280] 2015-07-12 22:18:10,992 Validator.java (line 242) Failed creating a merkle tree for [repair #d2178ba0-2902-11e5-bd95-f14c

Re: questions on cassandra (repair and multi-datacenter)

Hi Benjamin, I reverted back to the old RF of 2, by restarting all nodes with RF 2, and then running cleanup. It came down to 2. This time, i now changed the RF to 3 for all machines and restarted all the nodes. I started running repair one by one on all machines, tracking through jconsole that co

Re: questions on cassandra (repair and multi-datacenter)

Thanks Benjamin. I realised that, i have reverted using cleanup, got it back to old state and testing the scenario exactly the way you put it. On Thu, Sep 16, 2010 at 10:56 PM, Benjamin Black wrote: > On Thu, Sep 16, 2010 at 3:19 PM, Gurpreet Singh > wrote: > > 1. I was looking to increase the

Re: questions on cassandra (repair and multi-datacenter)

On Thu, Sep 16, 2010 at 3:19 PM, Gurpreet Singh wrote: > 1.  I was looking to increase the RF to 3. This process entails changing the > config and calling repair on the keyspace one at a time, right? > So, I started with one node at a time, changed the config file on the first > node for the keysp

questions on cassandra (repair and multi-datacenter)

Hi, I have a few questions and was looking for an answer. I have a cluster of 7 Cassandra 0.6.5 nodes in my test setup. RF=2. Original data size is about 100 gigs, with RF=2, i see the total load on the cluster is about 200 gigs, all good. 1. I was looking to increase the RF to 3. This process e