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/09/08 19:17:57 UTC
[jira] Created: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
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
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.
[jira] Commented: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773033#action_12773033 ]
Hudson commented on CASSANDRA-432:
----------------------------------
Integrated in Cassandra #247 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/247/])
scan on startup for orphaned filter and index files and remove them.
patch by Gary Dusbabek; reviewed by jbellis for
> 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
>
> Attachments: cassandra-432-v1.patch, cassandra-432-v2.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772613#action_12772613 ]
Gary Dusbabek commented on CASSANDRA-432:
-----------------------------------------
Yeah, not needed. It was leftover from a more complicated regex.
> 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
>
> Attachments: cassandra-432-v1.patch, cassandra-432-v2.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-432:
------------------------------------
Attachment: cassandra-432-v2.patch
removes redundant {1} from regex.
> 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
>
> Attachments: cassandra-432-v1.patch, cassandra-432-v2.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-432:
------------------------------------
Attachment: cassandra-432-v1.patch
Removes stray -Index.db and -Filter.db files.
> 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
>
> Attachments: cassandra-432-v1.patch
>
>
> 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.
[jira] Commented: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772611#action_12772611 ]
Jonathan Ellis commented on CASSANDRA-432:
------------------------------------------
isn't the {1} in the pattern redundant? or am i mis-remembering what it means? (i think it means "specify a count for the preceding item")
> 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
>
> Attachments: cassandra-432-v1.patch
>
>
> 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.
[jira] Assigned: (CASSANDRA-432) possible to have orphaned data
files that never get deleted
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-432:
----------------------------------------
Assignee: Gary Dusbabek
> 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.