cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6008) Getting 'This should never happen' error at startup due to sstables missing
Date Thu, 12 Dec 2013 17:12:12 GMT


Tyler Hobbs commented on CASSANDRA-6008:

bq. Right, but that should only affect purging range tombstones, since we write the row tombstone
based on emptyColumnFamily, not on the Reducer container.

Well, it's true that we'll still write out the row tombstone, but we'll fail to purge the
cells that it shadows (except for the first one), so the delete will appear to have worked,
but both the tombstone and cells will exist in the new sstable. After gcGrace has passed,
the row tombstone will be purged and any cells that remain will be revived.

> Getting 'This should never happen' error at startup due to sstables missing
> ---------------------------------------------------------------------------
>                 Key: CASSANDRA-6008
>                 URL:
>             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
> 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

View raw message