Re: What really happened during repair?

to the ML was that he was > already running full repair not incremental, which before 4.0 will also > performs anticompaction (unless you use subrange). > > Cheers, > > > > Le dim. 4 août 2019 à 02:29, Jeff Jirsa a écrit : > >> >> > On Aug 3, 2019, at 5:03 PM,

Re: What really happened during repair?

2019 at 10:29 AM Jeff Jirsa wrote: > > > On Aug 3, 2019, at 5:03 PM, Martin Xue wrote: > > > > Hi Cassandra community, > > > > I am using Cassandra 3.0.14, 1 cluster, node a,b,c in DC1, node d,e,f in > DC2. > > > > Keyspace_m is 1TB > > >

What really happened during repair?

Hi Cassandra community, I am using Cassandra 3.0.14, 1 cluster, node a,b,c in DC1, node d,e,f in DC2. Keyspace_m is 1TB When I run repair -pr a full keyspace_m on node a, what I noticed are: 1. Repair process is running on node a 2. Anti compaction after repair are running on other nodes at leas

Re: What happened about one node in cluster is down?

Thank you Jeff, appreciated. Regards Martin On Fri, Aug 2, 2019 at 10:52 PM Jeff Jirsa wrote: > > > > On Aug 2, 2019, at 5:47 AM, Oleksandr Shulgin < > oleksandr.shul...@zalando.de> wrote: > > > 3. what is the best strategy under this senario? >> >> Go to RF=3 or read and write at quorum so you

What happened about one node in cluster is down?

Hello, I am currently running into a production issue, and seek help from the community to help. Can anyone help with the following question regarding the Cassandra down node inside cluster? Case: Cassandra 3.0.14 3 nodes (A, B, C) in DC1, 3 nodes (D, E, F) in DC2 forming one cluster keyspace_m

Re: Repair failed and crash the node, how to bring it back?

ested with lots of > tombstones which in turn also tax on heap consumption. My $.002 cents for > the moment. > > > > > > > > *From:* Martin Xue [mailto:martin...@gmail.com] > *Sent:* Wednesday, July 31, 2019 5:05 PM > *To:* user@cassandra.apache.org > *Subject:*

Re: Repair failed and crash the node, how to bring it back?

/cassandra-reaper.io/> to > handle/schedule repairs. > > Cheers, > > - > Alexander Dejanovski > France > @alexanderdeja > > Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com > > > On Thu, Aug 1, 2019 at 12:05 AM Martin Xue wrote

Re: Repair failed and crash the node, how to bring it back?

-- > Alexander Dejanovski > France > @alexanderdeja > > Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com > > > On Wed, Jul 31, 2019 at 3:51 PM Martin Xue wrote: > >> Hi, >> >> I am running repair on production, star

Re: Repair / compaction for 6 nodes, 2 DC cluster

Sorry ASAD, don't have chance, still bogged down with the production issue... On Wed, Jul 31, 2019 at 10:56 PM ZAIDI, ASAD A wrote: > Did you get chance to look at tlp reaper tool i.e. > http://cassandra-reaper.io/ > > It is pretty awesome – Thanks to TLP team. > > >

Repair failed and crash the node, how to bring it back?

Hi, I am running repair on production, started with one of 6 nodes in the cluster (3 nodes in each of two DC). Cassandra version 3.0.14. running: repair -pr --full keyspace on node 1, 1TB data, takes two days, and crash, error shows: 3202]] finished (progress: 3%) Exception occurred during clean

Re: Repair / compaction for 6 nodes, 2 DC cluster

ng up. Shall I stop the anti-compaction process if it is too long? if so, how do I do it? Your help is much appreciated Thanks Regards Martin On Wed, Jul 31, 2019 at 9:18 PM Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On Wed, Jul 31, 2019 at 7:10 AM Martin Xue wro

Repair / compaction for 6 nodes, 2 DC cluster

Hello, Good day. This is Martin. Can someone help me with the following query regarding Cassandra repair and compaction? Currently we have a large keyspace (keyspace_event) with 1TB of data (in /var/lib/cassandra/data/keyspace_event); There is a cluster with Datacenter 1 contains 3 nodes, Data c

Re: Cassandra.Link Knowledge Base - v. 0.4

Thank you! On Sat, Jul 20, 2019 at 10:06 PM Rahul Singh wrote: > Hey Cassandra community , > > Thanks for all the feedback in the past on my cassandra knowledge base > project. Without the feedback cycle it’s not really for the community. > > *V. 0.1 - Awesome Cassandra readme.me