[
https://issues.apache.org/jira/browse/CASSANDRA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957136#comment-13957136
]
Russ Hatch commented on CASSANDRA-6971:
---------------------------------------
here's the schema output for the created keyspace (which all nodes don't "see"):
{noformat}
CREATE KEYSPACE ks WITH replication = {
'class': 'SimpleStrategy',
'replication_factor': '3'
};
USE ks;
CREATE TABLE cf (
key text PRIMARY KEY,
c counter
) WITH
bloom_filter_fp_chance=0.010000 AND
caching='KEYS_ONLY' AND
comment='test cf' AND
dclocal_read_repair_chance=0.000000 AND
gc_grace_seconds=864000 AND
read_repair_chance=0.100000 AND
replicate_on_write='true' AND
populate_io_cache_on_flush='false' AND
compaction={'class': 'SizeTieredCompactionStrategy'} AND
compression={'sstable_compression': 'SnappyCompressor'};
{noformat}
> nodes not seeing 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)
