Re: stalled nodetool repair?

Great! Many thanks On Thu, Aug 21, 2014 at 9:35 PM, Ben Bromhead wrote: > Ah sorry that is the original repo, see > https://github.com/BrianGallew/cassandra_range_repair for the updated > version of the script with vnode support > > Ben Bromhead > Instaclustr | www.instaclustr.com | @instaclust

Re: stalled nodetool repair?

Ah sorry that is the original repo, see https://github.com/BrianGallew/cassandra_range_repair for the updated version of the script with vnode support Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359 On 22 Aug 2014, at 2:19 pm, DuyHai Doan wrote: > Thanks Ben f

Re: stalled nodetool repair?

Thanks Ben for the link. Still this script does not work with vnodes, which exclude a wide range of C* config On Thu, Aug 21, 2014 at 5:51 PM, Ben Bromhead wrote: > https://github.com/mstump/cassandra_range_repair > > Also very useful. > > Ben Bromhead > Instaclustr | www.instaclustr.com | @ins

Re: stalled nodetool repair?

https://github.com/mstump/cassandra_range_repair Also very useful. Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359 On 22/08/2014, at 6:12 AM, Robert Coli wrote: > On Thu, Aug 21, 2014 at 12:32 PM, Kevin Burton wrote: > How do I watch the progress of nodetoo

Re: stalled nodetool repair?

On Thu, Aug 21, 2014 at 12:32 PM, Kevin Burton wrote: > How do I watch the progress of nodetool repair. > This is a very longstanding operational problem in Cassandra. Repair barely works and is opaque, yet one is expected to run it once a week in the default configuration. An unreasonably-host

Re: stalled nodetool repair?

If nodetool compactionstats says there are no Validation compactions running (and the compaction queue is empty) and netstats says there is nothing streaming there is a a good chance the repair is finished or dead. Source: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Is-it-saf

stalled nodetool repair?

How do I watch the progress of nodetool repair. Looks like the folklore from the list says to just use nodetool compactionstats nodetool netstats … but the repair seems locked/stalled and neither of these are showing any progress.. granted , this is a lot of data, but it would be nice to at lea

RE: Delete By Partition Key Implementation

If you delete entire row, do the records in the row still get counted towards computing TombstoneOverwhelmingException? It seems like they still do. From: DuyHai Doan [mailto:doanduy...@gmail.com] Sent: Saturday, August 09, 2014 3:21 AM To: user@cassandra.apache.org Subject: Re: Delete By Partit

Re: Latest 2.1 and Datastax driver questions...

On Wed, Aug 20, 2014 at 7:19 PM, Benedict Elliott Smith < belliottsm...@datastax.com> wrote: > The "run versions >= x.x.6" is IMO an out of date trope. Not only does 2.1 > have more than twice as many engineers working full time on it, and five > times the QA engineers (which is cumulative with pr

Re: Latest 2.1 and Datastax driver questions...

Thanks Tyler that is good to know. -Tony On Thursday, August 21, 2014 10:20 AM, Tyler Hobbs wrote: On Wed, Aug 20, 2014 at 3:44 PM, Tony Anecito wrote: > >Will there be a datastax CQL driver available then? The Python and C# drivers already have 2.1.0 versions available.  The Java d

Re: Latest 2.1 and Datastax driver questions...

On Wed, Aug 20, 2014 at 3:44 PM, Tony Anecito wrote: > > Will there be a datastax CQL driver available then? > The Python and C# drivers already have 2.1.0 versions available. The Java driver has a 2.1-rc release, and should have a 2.1.0 final release soon. -- Tyler Hobbs DataStax

Re: Manually deleting sstables

You can always set "autosnapshot: false" in cassandra.yaml for testing environments. On Thu, Aug 21, 2014 at 9:57 AM, Robert Wille wrote: > >> 2) Are there any other recommended procedures for this? >> > 0) stop writes to columnfamily > 1) TRUNCATE columnfamily; > 2) nodetool clearsnapshot

Re: Manually deleting sstables

> > 2) Are there any other recommended procedures for this? 0) stop writes to columnfamily 1) TRUNCATE columnfamily; 2) nodetool clearsnapshot # on the snapshot that results 3) DROP columnfamily; My two cents here is that this process is extremely difficult to automate, making testing that i