[
https://issues.apache.org/jira/browse/CASSANDRA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957166#comment-13957166
]
Russ Hatch commented on CASSANDRA-6971:
---------------------------------------
Yeah, I dislike adding pauses to dtests and agree with the idea of
CASSANDRA-6177.
I would prefer to block until schema agreement in this test rather than blindly
sleeping. But even with a manual pause of 2 minutes the 3 nodes don't arrive at
agreement. The ks is still not present in some nodes after this lengthy wait,
so I don't think the nodes are going to agree at all.
> nodes not catching up to creation of new keyspace
> -------------------------------------------------
>
> Key: CASSANDRA-6971
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6971
> Project: Cassandra
> Issue Type: Bug
> Reporter: Russ Hatch
>
> The dtest suite is running a test which creates a 3 node cluster, then adds a
> keyspace and column family. For some reason the 3 nodes are not agreeing on
> the schema version. The problem is intermittent -- either the nodes all agree
> on schema quickly, or they seem to stay stuck in limbo.
> The simplest way to reproduce is to run the dtest (simple_increment_test):
> https://github.com/riptano/cassandra-dtest/blob/master/counter_tests.py
> using nosetests:
> {noformat}
> nosetests -vs counter_tests.py:TestCounters.simple_increment_test
> {noformat}
> If the problem is reproduced nose will return this:
> ProgrammingError: Bad Request: Keyspace 'ks' does not exist
> I am not yet sure if the bug is reproducible outside of the dtest suite.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
