use https://github.com/BrianGallew/cassandra_range_repair
On 30 September 2014 05:24, Ken Hancock ken.hanc...@schange.com wrote:
On Mon, Sep 29, 2014 at 2:29 PM, Robert Coli rc...@eventbrite.com wrote:
As an aside, you just lose with vnodes and clusters of the size. I
presume you plan to
On Fri, Sep 26, 2014 at 9:52 AM, Gene Robichaux gene.robich...@match.com
wrote:
I am fairly new to Cassandra. We have a 9 node cluster, 5 in one DC and
4 in another.
Running a repair on a large column family seems to be moving much slower
than I expect.
Unfortunately, as others have
What is the recommendation on the number of tokens value? I am asking because
of the issue with sequential repairs on token range after token range.
Rahul Neelakantan
On Sep 29, 2014, at 2:29 PM, Robert Coli rc...@eventbrite.com wrote:
On Fri, Sep 26, 2014 at 9:52 AM, Gene Robichaux
On Mon, Sep 29, 2014 at 2:29 PM, Robert Coli rc...@eventbrite.com wrote:
As an aside, you just lose with vnodes and clusters of the size. I
presume you plan to grow over appx 9 nodes per DC, in which case you
probably do want vnodes enabled.
I typically only see discussion on vnodes vs.
Are you using Cassandra 2.0 vnodes? If so, repair takes forever.
This problem is addressed in 2.1.
On Fri, Sep 26, 2014 at 9:52 AM, Gene Robichaux
gene.robich...@match.com wrote:
I am fairly new to Cassandra. We have a 9 node cluster, 5 in one DC and 4 in
another.
Running a repair on a
Unfortunately DSE 4.5.0 is still on 2.0.x
-- Brice
On Fri, Sep 26, 2014 at 7:40 PM, Jonathan Haddad j...@jonhaddad.com wrote:
Are you using Cassandra 2.0 vnodes? If so, repair takes forever.
This problem is addressed in 2.1.
On Fri, Sep 26, 2014 at 9:52 AM, Gene Robichaux
With a 4.5 TB table and just 4 nodes, repair will likely take forever for
any version.
-Bryan
On Fri, Sep 26, 2014 at 10:40 AM, Jonathan Haddad j...@jonhaddad.com wrote:
Are you using Cassandra 2.0 vnodes? If so, repair takes forever.
This problem is addressed in 2.1.
On Fri, Sep 26,
Dutheil [mailto:brice.duth...@gmail.com]
Sent: Friday, September 26, 2014 12:47 PM
To: user@cassandra.apache.org
Subject: Re: Repair taking long time
Unfortunately DSE 4.5.0 is still on 2.0.x
-- Brice
On Fri, Sep 26, 2014 at 7:40 PM, Jonathan Haddad
j...@jonhaddad.commailto:j...@jonhaddad.com wrote
Subject: Re: Repair taking long time
Unfortunately DSE 4.5.0 is still on 2.0.x
-- Brice
On Fri, Sep 26, 2014 at 7:40 PM, Jonathan Haddad j...@jonhaddad.com wrote:
Are you using Cassandra 2.0 vnodes? If so, repair takes forever.
This problem is addressed in 2.1.
On Fri, Sep 26
Of
Jonathan Haddad
Sent: Friday, September 26, 2014 12:58 PM
To: user@cassandra.apache.org
Subject: Re: Repair taking long time
If you're using DSE you might want to contact Datastax support, rather than the
ML.
On Fri, Sep 26, 2014 at 10:52 AM, Gene Robichaux gene.robich...@match.com
wrote:
I am on DSE
Haddad
Sent: Friday, September 26, 2014 12:58 PM
To: user@cassandra.apache.org
Subject: Re: Repair taking long time
If you're using DSE you might want to contact Datastax support, rather than
the ML.
On Fri, Sep 26, 2014 at 10:52 AM, Gene Robichaux gene.robich...@match.com
wrote:
I am
11 matches
Mail list logo