cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5151) Implement better way of eliminating compaction left overs.
Date Fri, 18 Jan 2013 02:28:12 GMT


Jonathan Ellis commented on CASSANDRA-5151:

Flushing is roughly the same cost as the fsync you need to make sure the plain file is safely
written, so I don't see a performance penalty.  And I'm nervous about more one-off files (manifest
was bad enough).  Storing in the system table does seem cleaner to me.  Am I missing something
> 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
>            Assignee: Yuki Morishita
>             Fix For: 1.2.1
>         Attachments: 5151-1.2.txt
> 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