incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Meaning of 'nodetool repair has to run within GCGraceSeconds'
Date Fri, 08 Jul 2011 14:36:08 GMT
that's an internal term meaning "background i/o," not sstable merging per se.

On Fri, Jul 8, 2011 at 9:24 AM, A J <s5alye@gmail.com> wrote:
> I think node repair involves some compaction too. See the issue:
> https://issues.apache.org/jira/browse/CASSANDRA-2811
> It talks of 'validation compaction' being triggered concurrently
> during node repair.
>
> On Thu, Jun 30, 2011 at 8:51 PM, Watanabe Maki <watanabe.maki@gmail.com> wrote:
>> Repair doesn't compact. Those are different processes already.
>>
>> maki
>>
>>
>> On 2011/07/01, at 7:21, A J <s5alye@gmail.com> wrote:
>>
>>> Thanks all !
>>> In other words, I think it is safe to say that a node as a whole can
>>> be made consistent only on 'nodetool repair'.
>>>
>>> Has there been enough interest in providing anti-entropy without
>>> compaction as a separate operation (nodetool repair does both) ?
>>>
>>>
>>> On Thu, Jun 30, 2011 at 5:27 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
>>>> On Thu, Jun 30, 2011 at 3:47 PM, Edward Capriolo <edlinuxguru@gmail.com>
wrote:
>>>>> Read repair does NOT repair tombstones.
>>>>
>>>> It does, but you can't rely on RR to repair _all_ tombstones, because
>>>> RR only happens if the row in question is requested by a client.
>>>>
>>>> --
>>>> Jonathan Ellis
>>>> Project Chair, Apache Cassandra
>>>> co-founder of DataStax, the source for professional Cassandra support
>>>> http://www.datastax.com
>>>>
>>
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message