Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3EA6D9E79 for ; Mon, 31 Oct 2011 16:51:54 +0000 (UTC) Received: (qmail 21832 invoked by uid 500); 31 Oct 2011 16:51:54 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 21807 invoked by uid 500); 31 Oct 2011 16:51:54 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 21796 invoked by uid 99); 31 Oct 2011 16:51:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Oct 2011 16:51:54 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Oct 2011 16:51:52 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id C15E732A41F for ; Mon, 31 Oct 2011 16:51:32 +0000 (UTC) Date: Mon, 31 Oct 2011 16:51:32 +0000 (UTC) From: "Jonathan Ellis (Resolved) (JIRA)" To: commits@cassandra.apache.org Message-ID: <1195023238.41446.1320079892793.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1310254770.41346.1320079412786.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (CASSANDRA-3431) Cassandra Nodetool backup data restoration not working in clustered environment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-3431. --------------------------------------- Resolution: Not A Problem Operational questions should be asked on the users mailing list, not the bug tracker. > Cassandra Nodetool backup data restoration not working in clustered environment > ------------------------------------------------------------------------------- > > Key: CASSANDRA-3431 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3431 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 0.7.4 > Environment: Centos 5.5 64 bit > Reporter: Sunil Kumar > > Hi, > I have 2 cassandra cluster and each cluster have 2 nodes.Initially both cluster was running fine nodetool status show 2 node status up for each cluster. > Then I have taken backup of Cassandra first cluster of 2 nodes and restored it to second 2 nodes cluster. nodetool status got messed up now it is showing all 4 nodes as part of cluster on each nodes of both cluster. > I tried to debug this issue but not able to come up to solution. Please note that both cassandra clusters are running terremark ecloud. Is this SAN issue for node mess up???? > Then i found both cluster have same name in the cassandra.yaml. Then i changed the cluster name of second cluster. After that restore is not working both cassandra nodes are not coming up. they are throwing following error:- > ERROR [main] 2011-10-31 12:37:02,552 AbstractCassandraDaemon.java (line 131) Fatal exception during initialization > org.apache.cassandra.config.ConfigurationException: Saved cluster name Test Cluster != configured name grijes64 Cluster > at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:259) > at org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:127) > at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:314) > at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:79) > Please help me solving this issue thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira