Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 nicolas.lalevee@hibnet.org does not designate 216.86.168.183 as permitted
 sender)
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Dead node still being pinged
Date: Fri, 8 Jun 2012 14:10:40 +0200
Message-Id: <290D9F77-9EDD-4360-9A6C-635D41E99862@hibnet.org>
To: user@cassandra.apache.org
Mime-Version: 1.0 (Apple Message framework v1084)

I had a configuration where I had 4 nodes, data-1,4. We then bought 3 =
bigger machines, data-5,7. And we moved all data from data-1,4 to =
data-5,7.
To move all the data without interruption of service, I added one new =
node at a time. And then I removed one by one the old machines via a =
"remove token".

Everything was working fine. Until there was an expected load on our =
cluster, the machine started to swap and become unresponsive. We fixed =
the unexpected load and the three new machines were restarted. After =
that the new cassandra machines were stating that some old token were =
not assigned, namely from data-2 and data-4. To fix this I issued again =
some "remove token" commands.

Everything seems to be back to normal, but on the network I still see =
some packet from the new cluster to the old machines. On the port 7000.
How I can tell cassandra to completely forget about the old machines ?

Nicolas