Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of chihoub.houssem@gmail.com
 designates 209.85.160.172 as permitted sender)
MIME-Version: 1.0
Date: Tue, 17 Jan 2012 15:20:47 +0100
Message-ID: 
 <CAK03fLCUpcEVBfs7+Or1HZHU+aAA-nOsVeH146U=0pKMoS1_MQ@mail.gmail.com>
Subject: Can't find a keyspace created on a different node in the same
 cassandra cluster
From: Houssem Chihoub <chihoub.houssem@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001636eee1839903cc04b6ba09a4

--001636eee1839903cc04b6ba09a4
Content-Type: text/plain; charset=ISO-8859-1

Hello,

I deployed a 6 node cassandra cluster (cassandra-1.0.2) on Grid'5000 (the
french grid). I used hostnames instead of IPs.
When i create a new keyspace on one  cassandra node (i use the cassandra
client 'cassandra-cli') it's visible just on that node but not the others.

after the creation i get that it's agreed on in the cluster

CREATE KEYSPACE space1
...    ;
e4780dd0-4114-11e1-0000-242d50cf1fb7
Waiting for schema agreement...
... schemas agree across the cluster


When i run SHOW KEYSPACES on the same node i get this :

Keyspace: space1:
  Replication Strategy: org.apache.cassandra.locator.NetworkTopologyStrategy
  Durable Writes: true
    Options: [datacenter1:1]
  Column Families:

but on the other nodes i don't get anything and i can't use the already
created keyspace!!!

Here are some configuration parameters in cassandra.yaml is:

seeds: 'sol-7.sophia.grid5000.fr'
listen_address: localhost
rpc_address: 0.0.0.0
endpoint_snitch: org.apache.cassandra.locator.RackInferringSnitch
request_scheduler: org.apache.cassandra.scheduler.NoScheduler

Does anyone anyone know encountred this or knows how to solve this issue

Best regards

--001636eee1839903cc04b6ba09a4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,<br><br>I deployed a 6 node cassandra cluster (cassandra-1.0.2) on Gr=
id&#39;5000 (the french grid). I used hostnames instead of IPs.<br>When i c=
reate a new keyspace on one=A0 cassandra node (i use the cassandra client &=
#39;cassandra-cli&#39;) it&#39;s visible just on that node but not the othe=
rs.<br>
<br>after the creation i get that it&#39;s agreed on in the cluster <br><br=
>CREATE KEYSPACE space1<br>...=A0=A0=A0 ;<br>e4780dd0-4114-11e1-0000-242d50=
cf1fb7<br>Waiting for schema agreement...<br>... schemas agree across the c=
luster<br>
<br><br>When i run SHOW KEYSPACES on the same node i get this :<br><br>Keys=
pace: space1:<br>=A0 Replication Strategy: org.apache.cassandra.locator.Net=
workTopologyStrategy<br>=A0 Durable Writes: true<br>=A0=A0=A0 Options: [dat=
acenter1:1]<br>
=A0 Column Families:<br><br>but on the other nodes i don&#39;t get anything=
 and i can&#39;t use the already created keyspace!!!<br><br>Here are some c=
onfiguration parameters in cassandra.yaml is: <br><br>seeds: &#39;<a href=
=3D"http://sol-7.sophia.grid5000.fr">sol-7.sophia.grid5000.fr</a>&#39;<br>
listen_address: localhost<br>rpc_address: 0.0.0.0<br>endpoint_snitch: org.a=
pache.cassandra.locator.RackInferringSnitch<br>request_scheduler: org.apach=
e.cassandra.scheduler.NoScheduler<br><br>Does anyone anyone know encountred=
 this or knows how to solve this issue<br>
 <br>Best regards <br>

--001636eee1839903cc04b6ba09a4--