[ 
https://issues.apache.org/jira/browse/CASSANDRA-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845844#comment-13845844
 ] 

Tyler Hobbs commented on CASSANDRA-6008:
----------------------------------------

bq. I'm confused, I'm reading this as "LCR is not used in 2.0 unless imclib == 
0" but I'm sure that's not what you meant.

Sorry, I meant LCR wouldn't be used when compacting 
{{system.compactions_in_progress}} unless imclib == 0, because the 
max_compaction_threshold would prevent any row from getting that wide.

bq. I don't suppose you have a branch that pulls the renames into a separate 
commit?

I think what you're looking for is in [this 
branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-6008], specifically 
[this 
commit|https://github.com/thobbs/cassandra/commit/f0a68534835d76baf9fdec15438a178e0d8028b5]

> Getting 'This should never happen' error at startup due to sstables missing
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6008
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6008
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: John Carrino
>            Assignee: Tyler Hobbs
>             Fix For: 2.0.4
>
>         Attachments: 6008-2.0-v1.patch, 6008-trunk-v1.patch
>
>
> Exception encountered during startup: "Unfinished compactions reference 
> missing sstables. This should never happen since compactions are marked 
> finished before we start removing the old sstables"
> This happens when sstables that have been compacted away are removed, but 
> they still have entries in the system.compactions_in_progress table.
> Normally this should not happen because the entries in 
> system.compactions_in_progress are deleted before the old sstables are 
> deleted.
> However at startup recovery time, old sstables are deleted (NOT BEFORE they 
> are removed from the compactions_in_progress table) and then after that is 
> done it does a truncate using SystemKeyspace.discardCompactionsInProgress
> We ran into a case where the disk filled up and the node died and was bounced 
> and then failed to truncate this table on startup, and then got stuck hitting 
> this exception in ColumnFamilyStore.removeUnfinishedCompactionLeftovers.
> Maybe on startup we can delete from this table incrementally as we clean 
> stuff up in the same way that compactions delete from this table before they 
> delete old sstables.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to