cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Hatch (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6971) nodes not catching up to creation of new keyspace
Date Sat, 05 Apr 2014 01:17:14 GMT


Russ Hatch commented on CASSANDRA-6971:

weird, with the logging patch I didn't see any output from MigrationManager. I did see this
exception though (maybe was occuring before and I just didn't notice):
DEBUG [Thrift:2] 2014-04-04 19:03:59,051 (line 209) Thrift transport
error occurred during processing of message.
	at org.apache.thrift.transport.TTransport.readAll(
	at org.apache.thrift.transport.TFramedTransport.readFrame(
	at org.apache.thrift.transport.TTransport.readAll(
	at org.apache.thrift.protocol.TBinaryProtocol.readAll(
	at org.apache.thrift.protocol.TBinaryProtocol.readI32(
	at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(
	at org.apache.thrift.TBaseProcessor.process(
	at org.apache.cassandra.thrift.CustomTThreadPoolServer$
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$

> nodes not catching up to creation of new keyspace
> -------------------------------------------------
>                 Key: CASSANDRA-6971
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Russ Hatch
>         Attachments: 6971-debugging.txt, 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):
> using nosetests:
> {noformat}
> nosetests -vs
> {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

View raw message