cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manoj Kanta Mainali (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-5094) Should not reset local schema when there is no other nodes to resync
Date Fri, 28 Dec 2012 04:06:12 GMT
Manoj Kanta Mainali created CASSANDRA-5094:
----------------------------------------------

             Summary: Should not reset local schema when there is no other nodes to resync
                 Key: CASSANDRA-5094
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5094
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.1.7
            Reporter: Manoj Kanta Mainali


The nodetool resetlocalschema allows to drop the schema from a node. But, it does not check
whether there are other nodes present or not to resync the schema from. That means, if there
is only one instance, whether it is a single node or a cluster but other nodes were down,
and we reset the local schema the instance will not be able to resync from other nodes. In
that case, the node will not be able to serve requests. I haven't confirmed the behavior,
i.e. whether the instance will get the schema or not, when other nodes in the cluster come
back. However, in a single node cluster it will never be able to resync itself. 

It is better to check whether there are other nodes or not to resync from, and do not clear
the schemas if there are none.

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