cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2632) ConfigurationException when starting a node after deleting LocationInfo SStables
Date Wed, 11 May 2011 02:11:47 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-2632:
--------------------------------------

    Reviewer: slebresne

> ConfigurationException when starting a node after deleting LocationInfo SStables
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2632
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2632
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.5
>            Reporter: Aaron Morton
>            Assignee: Aaron Morton
>            Priority: Minor
>         Attachments: 0001-only-check-for-existing-LocationInfo-SSTables-during.patch
>
>
> from http://www.mail-archive.com/user@cassandra.apache.org/msg13170.html
> SystemTable.checkHealth() assumes that if the LOCATION_KEY row is not in the STATUS system
CF their should be no other files in the system data directory. If it's safe to delete the
LocationInfo sstables this stops the server restarting.
> I think the intention of the check is to assert that the reason the row was not found
is that there is no data in the STATUS CF. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message