Repair with "-pr" and vnodes

Hey guys, The documentation for the "-pr" repair option says it repairs only the first range returned by the partitioner. However, with vnodes a node owns a lot of small ranges. Does that mean that if I run rolling "nodetool repair -pr" on the cluster, a whole bunch of ranges remain un-repaired?

Re: High CPU usage on some of nodes

give it > a try. > > On Sep 10, 2015, at 1:43 PM, Robert Coli wrote: > > On Thu, Sep 10, 2015 at 10:54 AM, Roman Tkachenko > wrote: >> >> [5 second CMS GC] Is my best shot to play with JVM settings trying to >> tune garbage collection then? >> > > Ye

Re: High CPU usage on some of nodes

uot;user@cassandra.apache.org" , > > Date : 10/09/2015 15:30 > > Objet : Re: High CPU usage on some of nodes > > > > It sounds like its probably GC. Grep for GC in system.log to verify. > > If it is GC, there are a myriad of issues that could cause i

High CPU usage on some of nodes

Hey guys, We've been having issues in the past couple of days with CPU usage / load average suddenly skyrocketing on some nodes of the cluster, affecting performance significantly so majority of requests start timing out. It can go on for several hours, with CPU spiking through the roof then comin

Re: Overwhelming tombstones with LCS

015 at 1:40 PM, Roman Tkachenko > wrote: > >> Hey guys, >> >> I have a table with RF=3 and LCS. Data model makes use of "wide rows". A >> certain query run against this table times out and tracing reveals the >> following error on two out of three nodes:

Overwhelming tombstones with LCS

Hey guys, I have a table with RF=3 and LCS. Data model makes use of "wide rows". A certain query run against this table times out and tracing reveals the following error on two out of three nodes: *Scanned over 10 tombstones; query aborted (see tombstone_failure_threshold)* This basically me

Moving SSTables from one disk to another

Hey guys, We're running Cassandra with two data directories, let's say /data/sstables1 and /data/sstables2, which are in fact two separate (but identical) disks. The problem is that the disk where "sstables2" is mounted is running out of space and large SSTables stored there cannot be compacted.

Re: Deleted columns reappear after "repair"

Yep, good point: https://issues.apache.org/jira/browse/CASSANDRA-9045. On Thu, Mar 26, 2015 at 4:23 PM, Robert Coli wrote: > On Wed, Mar 25, 2015 at 6:53 PM, Roman Tkachenko > wrote: > >> Yup, I increased "in_memory_compaction_limit_in_mb" to 512MB so the row >&g

Re: Finding nodes that own a given token/partition key

Hi Dan, Have you tried using "nodetool getendpoints"? It shows you nodes that currently own the specific key. Roman On Thu, Mar 26, 2015 at 1:21 PM, Dan Kinder wrote: > Hey all, > > In certain cases it would be useful for us to find out which node(s) have > the data for a given token/partition

Re: Deleted columns reappear after "repair"

reason, that's unfortunate cause we have rows much larger than 512MB and it'd effectively mean nothing can be deleted from them... Can't increase this parameter forever. I'm gonna go ahead and file a report at JIRA. Roman On Wed, Mar 25, 2015 at 4:11 PM, Robert Coli wrote: >

Re: Deleted columns reappear after "repair"

issue? On Tue, Mar 24, 2015 at 11:00 AM, Roman Tkachenko wrote: > Well, as I mentioned in my original email all machines running Cassandra > are running NTP. This was one of the first things I verified and I triple > checked that they all show the same time. Is this sufficient to ensure &

Re: Deleted columns reappear after "repair"

Hi Roman, > > On 24/03/15 18:05, Roman Tkachenko wrote: > >> Hi Duncan, >> >> Thanks for the response! >> >> I can try increasing gc_grace_seconds and run repair on all nodes. It >> does not >> make sense though why all *new* deletes (for the same colum

Re: Deleted columns reappear after "repair"

every time delete happens? Also, how do I find out the value to set gc_grace_seconds to? Thanks. On Tue, Mar 24, 2015 at 9:38 AM, Duncan Sands wrote: > Hi Roman, > > On 24/03/15 17:32, Roman Tkachenko wrote: > >> Hey guys, >> >> Has anyone seen anything like this be

Re: Deleted columns reappear after "repair"

Hey guys, Has anyone seen anything like this behavior or has an explanation for it? If not, I think I'm gonna file a bug report. Thanks! Roman On Mon, Mar 23, 2015 at 4:45 PM, Roman Tkachenko wrote: > Hey guys, > > We're having a very strange issue: deleted columns g

Deleted columns reappear after "repair"

Hey guys, We're having a very strange issue: deleted columns get resurrected when "repair" is run on a node. Info about the setup. Cassandra 2.0.13, multi datacenter with 12 nodes in one datacenter and 6 nodes in another one. Schema: cqlsh> describe keyspace blackbook; CREATE KEYSPACE blackbook