cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4872) Move manifest into sstable metadata
Date Wed, 13 Feb 2013 19:16:13 GMT

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

Marcus Eriksson commented on CASSANDRA-4872:
--------------------------------------------

there should be a tool to offline-drop all files back to L0, that is a "common" thing we have
done a few times in production (by removing the .json file)

ill do that as a separate ticket if this gets committed
                
> Move manifest into sstable metadata
> -----------------------------------
>
>                 Key: CASSANDRA-4872
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4872
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v1.patch
>
>
> Now that we have a metadata component it would be better to keep sstable level there,
than in a separate manifest.  With information per-sstable we don't need to do a full re-level
if there is corruption.

--
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

Mime
View raw message