[
https://issues.apache.org/jira/browse/CASSANDRA-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548947#comment-13548947
]
Jonathan Ellis commented on CASSANDRA-5137:
-------------------------------------------
Something like this...
{code}
create table compaction_log (
id uuid primary key,
inputs set<int>,
outputs set<int>
);
{code}
When we start a compaction, we add it to the log. When we finish, we remove
it. If we restart and compaction_log is not empty, we remove any sstables from
the outputs set.
> Make sure SSTables left over from compaction get deleted and logged
> -------------------------------------------------------------------
>
> Key: CASSANDRA-5137
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5137
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.3
> Reporter: Yuki Morishita
> Assignee: Yuki Morishita
> Priority: Minor
> Fix For: 1.1.9, 1.2.1
>
> Attachments: 5137-1.1.txt
>
>
> When opening ColumnFamily, cassandra checks SSTable files' ancestors and
> skips loading already compacted ones. Those files are expected to be deleted,
> but currently that never happens.
> Also, there is no indication of skipping loading file in the log, so it is
> confusing especially doing upgradesstables.
--
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: http://www.atlassian.com/software/jira
