[
https://issues.apache.org/jira/browse/CASSANDRA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960834#comment-13960834
]
Russ Hatch commented on CASSANDRA-6971:
---------------------------------------
Here's the gossipinfo output. This is several minutes after the test failed.
Schema uuid's still mismatch.
{noformat}
rhatch@whatup:/tmp/dtest-VZ3n7v/test/node1$ bin/nodetool -p 7100 gossipinfo
/127.0.0.2
DC:datacenter1
HOST_ID:8929d0a0-5a4f-4a6f-85c3-665bb3aaf140
SCHEMA:19969d6d-daaa-328f-ade0-8640043e37b9
NET_VERSION:6
RPC_ADDRESS:127.0.0.2
RACK:rack1
LOAD:52150.0
STATUS:NORMAL,-3074457345618258603
RELEASE_VERSION:1.2.0-SNAPSHOT
/127.0.0.3
DC:datacenter1
SCHEMA:59adb24e-f3cd-3e02-97f0-5b395827453f
HOST_ID:864a00d4-f661-421e-81c3-90e7b8f90ef1
NET_VERSION:6
RPC_ADDRESS:127.0.0.3
RACK:rack1
LOAD:14361.0
STATUS:NORMAL,3074457345618258602
RELEASE_VERSION:1.2.0-SNAPSHOT
/127.0.0.1
DC:datacenter1
HOST_ID:06bbda3d-5265-4134-8248-11e0a2ddf798
RPC_ADDRESS:127.0.0.1
NET_VERSION:6
SCHEMA:19969d6d-daaa-328f-ade0-8640043e37b9
RACK:rack1
LOAD:52153.0
STATUS:NORMAL,-9223372036854775808
RELEASE_VERSION:1.2.0-SNAPSHOT
rhatch@whatup:/tmp/dtest-VZ3n7v/test/node1$ bin/nodetool -p 7200 gossipinfo
/127.0.0.2
HOST_ID:8929d0a0-5a4f-4a6f-85c3-665bb3aaf140
SCHEMA:19969d6d-daaa-328f-ade0-8640043e37b9
NET_VERSION:6
LOAD:52150.0
RPC_ADDRESS:127.0.0.2
RACK:rack1
DC:datacenter1
RELEASE_VERSION:1.2.0-SNAPSHOT
STATUS:NORMAL,-3074457345618258603
/127.0.0.3
HOST_ID:864a00d4-f661-421e-81c3-90e7b8f90ef1
SCHEMA:59adb24e-f3cd-3e02-97f0-5b395827453f
NET_VERSION:6
LOAD:14361.0
RPC_ADDRESS:127.0.0.3
RACK:rack1
DC:datacenter1
RELEASE_VERSION:1.2.0-SNAPSHOT
STATUS:NORMAL,3074457345618258602
/127.0.0.1
HOST_ID:06bbda3d-5265-4134-8248-11e0a2ddf798
SCHEMA:19969d6d-daaa-328f-ade0-8640043e37b9
NET_VERSION:6
LOAD:52153.0
RPC_ADDRESS:127.0.0.1
RACK:rack1
DC:datacenter1
RELEASE_VERSION:1.2.0-SNAPSHOT
STATUS:NORMAL,-9223372036854775808
rhatch@whatup:/tmp/dtest-VZ3n7v/test/node1$ bin/nodetool -p 7300 gossipinfo
/127.0.0.2
NET_VERSION:6
RELEASE_VERSION:1.2.0-SNAPSHOT
DC:datacenter1
SCHEMA:19969d6d-daaa-328f-ade0-8640043e37b9
HOST_ID:8929d0a0-5a4f-4a6f-85c3-665bb3aaf140
LOAD:52150.0
STATUS:NORMAL,-3074457345618258603
RACK:rack1
RPC_ADDRESS:127.0.0.2
/127.0.0.3
NET_VERSION:6
RELEASE_VERSION:1.2.0-SNAPSHOT
DC:datacenter1
SCHEMA:59adb24e-f3cd-3e02-97f0-5b395827453f
HOST_ID:864a00d4-f661-421e-81c3-90e7b8f90ef1
LOAD:14361.0
STATUS:NORMAL,3074457345618258602
RACK:rack1
RPC_ADDRESS:127.0.0.3
/127.0.0.1
NET_VERSION:6
RELEASE_VERSION:1.2.0-SNAPSHOT
DC:datacenter1
SCHEMA:19969d6d-daaa-328f-ade0-8640043e37b9
HOST_ID:06bbda3d-5265-4134-8248-11e0a2ddf798
LOAD:52153.0
STATUS:NORMAL,-9223372036854775808
RACK:rack1
RPC_ADDRESS:127.0.0.1
{noformat}
> 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: node1.log, node2.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)
