[
https://issues.apache.org/jira/browse/CASSANDRA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-6971:
----------------------------------------
Attachment: 6971.txt
My guess is that passiveAnnounce hasn't been called in time when the
onAlive/onRestart events have been called closely enough, so we need to also
check onChange. Patch to do so, plus the debugging.
> 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
> Attachments: 6971-debugging.txt, 6971.txt, debug1.log, debug2.log,
> debug3.log, node1.log, node1.log, node2.log, node2.log, node3.log, node3.log
>
>
> 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)
