Well, in that case, you may want to roll your own script for doing constant repairs of your cluster, and extend your gc grace seconds so you can repair the whole cluster before the tombstones are cleared.
On Fri, Sep 26, 2014 at 11:15 AM, Gene Robichaux <gene.robich...@match.com> wrote: > Using their community edition......no support (yet!) :( > > Gene Robichaux > Manager, Database Operations > Match.com > 8300 Douglas Avenue I Suite 800 I Dallas, TX 75225 > Phone: 214-576-3273 > > -----Original Message----- > From: jonathan.had...@gmail.com [mailto:jonathan.had...@gmail.com] On Behalf > 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 4.0.3 which is 2.0.7. >> >> >> >> If 4.5.1 is NOT 2.1. I guess an upgrade will not buy me much….. >> >> >> >> The bad thing is that table is not our largest….. :( >> >> >> >> >> >> Gene Robichaux >> >> Manager, Database Operations >> >> Match.com >> >> 8300 Douglas Avenue I Suite 800 I Dallas, TX 75225 >> >> Phone: 214-576-3273 >> >> >> >> From: Brice 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.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 >> <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. >>> >>> >>> >>> Looking at nodetool compaction stats it indicates the Validation >>> phase is running that the total bytes is 4.5T (4505336278756). >>> >>> >>> >>> This is a very large CF. The process has been running for 2.5 hours >>> and has processed 71G (71950433062). That rate is about 28.4 GB per >>> hour. At this rate it will take 158 hours, just shy of 1 week. >>> >>> >>> >>> Is this reasonable? This is my first large repair and I am wondering >>> if this is normal for a CF of this size. Seems like a long time to >>> me. >>> >>> >>> >>> Is it possible to tune this process to speed it up? Is there >>> something in my configuration that could be causing this slow >>> performance? I am running HDDs, not SSDs in a JBOD configuration. >>> >>> >>> >>> >>> >>> >>> >>> Gene Robichaux >>> >>> Manager, Database Operations >>> >>> Match.com >>> >>> 8300 Douglas Avenue I Suite 800 I Dallas, TX 75225 >>> >>> Phone: 214-576-3273 >>> >>> >> >> >> -- >> Jon Haddad >> http://www.rustyrazorblade.com >> twitter: rustyrazorblade >> >> > > > > -- > Jon Haddad > http://www.rustyrazorblade.com > twitter: rustyrazorblade -- Jon Haddad http://www.rustyrazorblade.com twitter: rustyrazorblade
