cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anubhav Kale (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-11142) Confusing error message on schema updates when nodes are down
Date Tue, 09 Feb 2016 23:42:18 GMT
Anubhav Kale created CASSANDRA-11142:
----------------------------------------

             Summary: Confusing error message on schema updates when nodes are down
                 Key: CASSANDRA-11142
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11142
             Project: Cassandra
          Issue Type: Bug
         Environment: PROD
            Reporter: Anubhav Kale
            Priority: Minor


Repro steps are as follows (this was tested on Windows and is a consistent repro)

. Start a two node cluster.
. Ensure that "nodetool status" shows both nodes as UN on both nodes
. Stop Node2
. Ensure that "nodetool status" shows that Node2 in DN.
. Start cqlsh on Node1
. Create a table
. cqlsh times out with below message (coming from .py)

Warning: schema version mismatch detected, which might be caused by DOWN nodes; if this is
not the case, check the schema versions of your nodes in system.local and system.peers.
OperationTimedOut: errors={}, last_host=10.1.0.10
. Do a select * on the table that just timed out. It works fine.

It just seems odd that there are no errors, but the table gets created fine. We should either
fix the timeout exception with a real error or not throw timeout. Not sure what the best approach
is.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message