You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2014/02/04 23:30:11 UTC
[jira] [Created] (CASSANDRA-6650) Bootstrapped nodes don't know
about existing keyspaces
Ryan McGuire created CASSANDRA-6650:
---------------------------------------
Summary: Bootstrapped nodes don't know about existing keyspaces
Key: CASSANDRA-6650
URL: https://issues.apache.org/jira/browse/CASSANDRA-6650
Project: Cassandra
Issue Type: Bug
Reporter: Ryan McGuire
Bootstrapping a new node in a cluster has no knowledge of the existing keyspaces.
{code}
ccm create -v git:cassandra-1.2.14 bootstrap_bug
ccm populate -n 3
ccm start
ccm node1 stress -n 10000
# Bootstrap a new node:
ccm add -b node4 -t 127.0.0.4:9160 -l 127.0.0.4:7000 -j 7400 --binary-itf 127.0.0.4:9042
ccm node4 start
# Query data from the new node:
ccm node4 cqlsh
cqlsh> select * from "Keyspace1"."Standard1" limit 10;
Bad Request: Keyspace Keyspace1 does not exist
{code}
This scenario works fine on 1.2.13 and I have not reproduced this in 2.0.x, so this must be something specific to the 1.2.14 release.
I've uploaded the logs from node4 from 1.2.13 and 1.2.14. In 1.2.13 we see:
{code}
INFO [InternalResponseStage:1] 2014-02-04 16:51:40,578 ColumnFamilyStore.java (line 223) Initializing Keyspace1.Standard1
{code}
But no such lines in the 1.2.14 logs.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)