cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5151) Implement better way of eliminating compaction left overs.
Date Thu, 17 Jan 2013 17:32:12 GMT


Yuki Morishita commented on CASSANDRA-5151:

We want to remove left-overs before opening CFs by reading compaction log system CF. The problem
is, commit log has to be recovered before reading from any CF, but CF initialization should
be completed before commit log recovery. So there is no chance to scrub off left-overs before
CF init. Obviously we don't want to flush every time we update compaction log.

Alternative way is to write compaction log file with inputs each time we start compaction,
and remove it when complete.
If CF sees that compaction log files in its data directory, that means there are unfinished
compactions and those sstable files with ancestors that are in compaction log files should
be deleted. Does this sound likely to work?
> Implement better way of eliminating compaction left overs.
> ----------------------------------------------------------
>                 Key: CASSANDRA-5151
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>            Reporter: Yuki Morishita
>             Fix For: 1.2.1
> This is from discussion in CASSANDRA-5137. Currently we skip loading SSTables that are
left over from incomplete compaction to not over-count counter, but the way we track compaction
completion is not secure.
> One possible solution is to create system CF like:
> {code}
> create table compaction_log (
>   id uuid primary key,
>   inputs set<int>,
>   outputs set<int>
> );
> {code}
> to track incomplete compaction.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message