You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/10/21 21:54:59 UTC

[jira] Commented: (CASSANDRA-432) possible to have orphaned data files that never get deleted

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

Jonathan Ellis commented on CASSANDRA-432:
------------------------------------------

(refering to ColumnFamilyStore.onStart and SSTable.delete)

> possible to have orphaned data files that never get deleted
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-432
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-432
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.5
>
>
> startup looks for data files, then tries to load them
> delete removes starting w/ the data file (so that if there is a partial delete, we don't panic on the next start b/c of missing index or bloom filter)
> but this means that if we have a partial delete, the index/BF files can persist forever

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.