Return-Path: 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 4B8447FFE for ; Sat, 10 Sep 2011 19:53:48 +0000 (UTC) Received: (qmail 24001 invoked by uid 500); 10 Sep 2011 19:53:46 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 23967 invoked by uid 500); 10 Sep 2011 19:53:46 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 23950 invoked by uid 99); 10 Sep 2011 19:53:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Sep 2011 19:53:41 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yiming.sun@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Sep 2011 19:53:36 +0000 Received: by wwf5 with SMTP id 5so1784623wwf.25 for ; Sat, 10 Sep 2011 12:53:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=IWSj/Rl395Wb+8kEyp3MFYWZta3YkzWx45SIrz2wI30=; b=OmUvWBbSdPtnCf1/3KlCFQv2/4qQlHWRrMtp+SUn01ywFA1Kruks6ulfcf2WZ4Ljtv +6P7UCmLEwdNxvTh18A+p/M+tdcTJES4tVTgjA+B3IUSnWrKJtILxhf0wtMkVFe+3yxI hyrtCXPYFtYAkUCYZTABJofWC+qwxs9dldXrE= Received: by 10.216.87.3 with SMTP id x3mr718606wee.82.1315684395207; Sat, 10 Sep 2011 12:53:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.166.79 with HTTP; Sat, 10 Sep 2011 12:52:55 -0700 (PDT) In-Reply-To: References: From: Yiming Sun Date: Sat, 10 Sep 2011 15:52:55 -0400 Message-ID: Subject: Re: mysterious data disappearance - what happened? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016e6d7e89a034eb904ac9ba578 --0016e6d7e89a034eb904ac9ba578 Content-Type: text/plain; charset=ISO-8859-1 Hi Peter, Good call! I went and checked the seed, and indeed it left unchanged when we copied the config yaml file from the first node to the second node. Thanks! -- Y. On Fri, Sep 9, 2011 at 7:47 PM, Peter Schuller wrote: > > cluster name for both machines. So in other words, if we want to launch > two > > separate instances of cassandra and keep them separate, we must make sure > > each uses a different cluster name or else they will gang up into the > same > > cluster? But how do they even discover each other? Can someone > enlighten > > me please? Thanks. > > It is highly recommended to use distinct cluster names, in particular > because it can help avoid accidentally "merging" two independent > clusters. > > As for how it happened: There is no magic discovery going on that > would pick IP:s at random, but one could certainly e.g. accidentally > configure the seed node on one to point to the other or some such. > > (1) does nodetool -h localhost ring show an unexpected node? > (2) i'd suggest checking system.log on each node for the first > appearance (if any) of the "unexpected" ip address and correlate (by > time) with what happened on the other node (was it restarted at the > time for example, potentially wth a bad conf?) > (3) are these two single-instance cassandras that have never > participated in another cluster? > > -- > / Peter Schuller (@scode on twitter) > --0016e6d7e89a034eb904ac9ba578 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Peter,

Good call! I went and checked the seed, and in= deed it left unchanged when we copied the config yaml file from the first n= ode to the second node. =A0Thanks!

-- Y.

On Fri, Sep 9, 2011 at 7:47 PM, Peter Schuller <peter.schuller@infidyne.com>= ; wrote:
> cluster name for both machines. =A0So in other words= , if we want to launch two
> separate instances of cassandra and keep them separate, we must make s= ure
> each uses a different cluster name or else they will gang up into the = same
> cluster? =A0But how do they even discover each other? =A0Can someone e= nlighten
> me please? =A0Thanks.

It is highly recommended to use distinct cluster names, in particular=
because it can help avoid accidentally "merging" two independent<= br> clusters.

As for how it happened: There is no magic discovery going on that
would pick IP:s at random, but one could certainly e.g. accidentally
configure the seed node on one to point to the other or some such.

(1) does nodetool -h localhost ring show an unexpected node?
(2) i'd suggest checking system.log on each node for the first
appearance (if any) of the "unexpected" ip address and correlate = (by
time) with what happened on the other node (was it restarted at the
time for example, potentially wth a bad conf?)
(3) are these two single-instance cassandras that have never
participated in another cluster?

--
/ Peter Schuller (@scode on twitter)

--0016e6d7e89a034eb904ac9ba578--