Return-Path: 
 <user-return-26958-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 68399C50D
	for <apmail-cassandra-user-archive@www.apache.org>;
 Wed, 13 Jun 2012 14:07:42 +0000 (UTC)
Received: (qmail 45780 invoked by uid 500); 13 Jun 2012 14:07:40 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 45756 invoked by uid 500); 13 Jun 2012 14:07:40 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 45747 invoked by uid 99); 13 Jun 2012 14:07:40 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 14:07:40 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FSL_RCVD_USER,HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of cyril.auburtin@gmail.com
 designates 209.85.160.172 as permitted sender)
Received: from [209.85.160.172] (HELO mail-gh0-f172.google.com)
 (209.85.160.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 14:07:33 +0000
Received: by ghbg16 with SMTP id g16so483749ghb.31
        for <user@cassandra.apache.org>; Wed, 13 Jun 2012 07:07:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=hmsluqHhrBc794O6CXYCQIgH4++TTN1+/dgf2QBh/DA=;
        b=ZR2XBCBtUeuopfzg8Crt4+K1+2KFk8hOzO2B+SHQ+Zox89fsba1PNpyap6m1NZtgVe
         UdqiE3oJSY/7o74DPyAQp3JA/oBb5cf21UoOcebgsDbYFpJzOGS37gb0qyilKi43kR0c
         FIweHizEwXVOjUTePAG2Hzv1M0YuO061tzmtkf+eQx5QOnC6DgRtauMWQ9Bck7sDCIWk
         7/5U4YepKF3LX06DrUnCYh+tzrDM2NKENWNXOT6WubJBGIVoxYm9u5Xhr0X2fP+2GgL2
         0O0V2J37GNUL8Ic0x7KmrW/g1fBu8QAYRKnh9e2InZywyYedwUDKR4VFnStkSmqdJ64f
         TEgQ==
Received: by 10.236.176.5 with SMTP id a5mr33239025yhm.67.1339596432035; Wed,
 13 Jun 2012 07:07:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.195.2 with HTTP; Wed, 13 Jun 2012 07:06:50 -0700 (PDT)
From: Cyril Auburtin <cyril.auburtin@gmail.com>
Date: Wed, 13 Jun 2012 16:06:50 +0200
Message-ID: 
 <CAKteAhGxKm-aS8-tKg-k9T4MUtuPRLSRZz66ScaQ=gQnco24vg@mail.gmail.com>
Subject: cassandra still tried to join old ring nodes
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf302ef836794e4204c25b1988

--20cf302ef836794e4204c25b1988
Content-Type: text/plain; charset=ISO-8859-1

I joined a ring, then left it

now my local ring is just showing my local cassndra node, like intended

but on the cassandra -f process, It keeps sending every 5 seconds

WARN 16:01:44,042 ClusterName mismatch from /123.123.123.123 big
cluster!=Test Cluster

where big cluster is the cluster name used when in the previous ring


Why do I keep receiving this alerts? is it because 123.123.123.123 still
tries to be in the ring?
Should I run nodetool decommission (token that had my node) on that node?
to stop this alert?

thx for explanations

--20cf302ef836794e4204c25b1988
Content-Type: text/html; charset=ISO-8859-1

I joined a ring, then left it<div><br></div><div>now my local ring is just showing my local cassndra node, like intended</div><div><br></div><div>but on the cassandra -f process, It keeps sending every 5 seconds</div><div>

<br></div><div>WARN 16:01:44,042 ClusterName mismatch from /<a href="http://123.123.123.123">123.123.123.123</a> big cluster!=Test Cluster</div><div><br></div><div>where big cluster is the cluster name used when in the previous ring</div>

<div><br></div><div><br></div><div>Why do I keep receiving this alerts? is it because 123.123.123.123 still tries to be in the ring?</div><div>Should I run nodetool decommission (token that had my node) on that node? to stop this alert?</div>

<div><br></div><div>thx for explanations</div><div><br></div>

--20cf302ef836794e4204c25b1988--