You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aaron Morton (JIRA)" <ji...@apache.org> on 2011/05/11 03:20:47 UTC
[jira] [Created] (CASSANDRA-2632) ConfigurationException when
starting a node after deleting LocationInfo SStables
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
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
[jira] [Updated] (CASSANDRA-2632) ConfigurationException when
starting a node after deleting LocationInfo SStables
Posted by "Aaron Morton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Morton updated CASSANDRA-2632:
------------------------------------
Attachment: 0001-only-check-for-existing-LocationInfo-SSTables-during.patch
Attached patch checks the SSTable count for the STATUS CF to determine if the reason the location info was not found was because the partitioner changed.
> 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
[jira] [Updated] (CASSANDRA-2632) ConfigurationException when
starting a node after deleting LocationInfo SStables
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-2632) ConfigurationException when
starting a node after deleting LocationInfo SStables
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031616#comment-13031616 ]
Hudson commented on CASSANDRA-2632:
-----------------------------------
Integrated in Cassandra-0.7 #477 (See [https://builds.apache.org/hudson/job/Cassandra-0.7/477/])
Allow removing LocationInfo sstables (to allow cluster rename)
patch by amorton; reviewed by slebresne for CASSANDRA-2632
> 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
> Fix For: 0.7.6
>
> 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