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 sorin.julean@gmail.com
 designates 209.85.161.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADdsq2Lt5NKMn5qrsxxg6fHEDz=KCmNxoeeej2ejp+h3EeLn-w@mail.gmail.com>
References: 
 <CADdsq2Lt5NKMn5qrsxxg6fHEDz=KCmNxoeeej2ejp+h3EeLn-w@mail.gmail.com>
Date: Tue, 2 Aug 2011 15:12:25 +0100
Message-ID: 
 <CAJYbC8uRsYNgLo2xTaKXZPpPhko=izFWdtE=gLZ6KRFYh-fZRg@mail.gmail.com>
Subject: Re: Nodetool ring not showing all nodes in cluster
From: Sorin Julean <sorin.julean@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=002354187e6c46db9a04a98656c8

--002354187e6c46db9a04a98656c8
Content-Type: text/plain; charset=ISO-8859-1

Hi,

 Until someone answers  with more details, few questions:
 1. did you moved the system keyspace as well ?
 2. the gossip IP of the new nodes are the same as the old ones ?
 3. which cassandra version are you running ?

If 1. is yes and 2. is no, for a quick fix: take down the cluster, remove
system keyspace, bring the cluster up and bootstrap the nodes.


Kind regards,
Sorin


On Tue, Aug 2, 2011 at 2:53 PM, Aishwarya Venkataraman <cyberaishu@gmail.com
> wrote:

> Hello,
>
> I recently migrated 400 GB of data that was on a different cassandra
> cluster (3 node with RF= 3) to a new cluster. I have a 3 node  cluster
> with replication factor set to three. When I run nodetool ring, it
> does not show me all the nodes in the cluster. It always keeps showing
> only one node and mentions that it is handling 100% of the load. But
> when I look at the logs, the nodes are able to talk to each other via
> the gossip protocol. Why does this happen ? Can you tell me what I am
> doing wrong ?
>
> Thanks,
> Aishwarya
>

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

Hi,<br><br>=A0Until someone answers=A0 with more details, few questions:<br=
>=A01. did you moved the system keyspace as well ?<br>=A02. the gossip IP o=
f the new nodes are the same as the old ones ?<br>=A03. which cassandra ver=
sion are you running ?<br>
<br>If 1. is yes and 2. is no, for a quick fix: take down the cluster, remo=
ve system keyspace, bring the cluster up and bootstrap the nodes.<br><br><b=
r>Kind regards,<br>Sorin<br><br><br><div class=3D"gmail_quote">On Tue, Aug =
2, 2011 at 2:53 PM, Aishwarya Venkataraman <span dir=3D"ltr">&lt;<a href=3D=
"mailto:cyberaishu@gmail.com">cyberaishu@gmail.com</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hello,<br>
<br>
I recently migrated 400 GB of data that was on a different cassandra<br>
cluster (3 node with RF=3D 3) to a new cluster. I have a 3 node =A0cluster<=
br>
with replication factor set to three. When I run nodetool ring, it<br>
does not show me all the nodes in the cluster. It always keeps showing<br>
only one node and mentions that it is handling 100% of the load. But<br>
when I look at the logs, the nodes are able to talk to each other via<br>
the gossip protocol. Why does this happen ? Can you tell me what I am<br>
doing wrong ?<br>
<br>
Thanks,<br>
<font color=3D"#888888">Aishwarya<br>
</font></blockquote></div><br>

--002354187e6c46db9a04a98656c8--