cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5051) Allow automatic cleanup after gc_grace
Date Tue, 05 Nov 2013 17:10:22 GMT


Chris Burroughs commented on CASSANDRA-5051:


"Yo we added some more nodes why is performance not better yet" is a fairly common complaint
I get.   That said of: (A) status quo; (B) auto-cleanup after X; (C) auto-cleanup all the
time. I'd welcome the option for (B) and probably enable it on all current clusters, but I
can't think of a cluster where I would prefer (C) over (A).  Even a small risk of dealing
with a backup/restore situation is not worth it.

> Allow automatic cleanup after gc_grace
> --------------------------------------
>                 Key: CASSANDRA-5051
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Vijay
>              Labels: vnodes
>             Fix For: 2.1
>         Attachments: 0001-5051-v4.patch, 0001-5051-v6.patch, 0001-5051-with-test-fixes.patch,
0001-CASSANDRA-5051.patch, 0002-5051-remove-upgradesstable-v4.patch, 0002-5051-remove-upgradesstable.patch,
0004-5051-additional-test-v4.patch, 5051-v2.txt
> When using vnodes, after adding a new node you have to run cleanup on all the machines,
because you don't know which are affected and chances are it was most if not all of them.
 As an alternative to this intensive process, we could allow cleanup during compaction if
the data is older than gc_grace (or perhaps some other time period since people tend to use
gc_grace hacks to get rid of tombstones.)

This message was sent by Atlassian JIRA

View raw message