On Wed, Oct 12, 2011 at 3:51 PM, Jonathan Ellis wrote:
> Well, the reason you'd want to run repair is to get the tombstone on
> nodes that missed the insert. And that would only be important if you
> sometimes generate inserts that would be otherwise shadowed by the
> tombstone, right?
The initi
Well, the reason you'd want to run repair is to get the tombstone on
nodes that missed the insert. And that would only be important if you
sometimes generate inserts that would be otherwise shadowed by the
tombstone, right?
On Wed, Oct 12, 2011 at 2:17 AM, Sylvain Lebresne wrote:
> Unfortunately
On 10/11/2011 09:49 PM, Terry Cumaranatunge wrote:
Hello,
If you set a ttl and expire a column, I've read that this eventually
turns into a tombstone and will be cleaned out by the GC. Are
expirations considered a form of delete that still requires a node
repair to be run in gc_grace_period se
Unfortunately, expiring column are no magic bullet. If you insert
columns with ttl=1,
you're roughly doing the same thing than deleting, so the exact same
rule concerning
repair applies.
What can be said on repair and expiring columns (and that may or may
not be helpful)
is that if you have a colu
Hello,
If you set a ttl and expire a column, I've read that this eventually turns
into a tombstone and will be cleaned out by the GC. Are expirations
considered a form of delete that still requires a node repair to be run in
gc_grace_period seconds? The operations guide says you have to run node
r