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 D11801066F for ; Wed, 25 Sep 2013 20:00:02 +0000 (UTC) Received: (qmail 55528 invoked by uid 500); 25 Sep 2013 19:59:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55514 invoked by uid 500); 25 Sep 2013 19:59:58 -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 55506 invoked by uid 99); 25 Sep 2013 19:59:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 19:59:57 +0000 X-ASF-Spam-Status: No, hits=-6.5 required=5.0 tests=ENV_AND_HDR_SPF_MATCH,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,USER_IN_DEF_SPF_WL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michael.laing@nytimes.com designates 209.85.220.47 as permitted sender) Received: from [209.85.220.47] (HELO mail-pa0-f47.google.com) (209.85.220.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 19:59:50 +0000 Received: by mail-pa0-f47.google.com with SMTP id kp14so290225pab.34 for ; Wed, 25 Sep 2013 12:59:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=i1fujYRaPBlCFEVvqQz6ZZjDCfCdzWlITVJze4j4Pws=; b=mHPFAHK7RflHbHAh3j+q8SZiuOQ7SzpUc1OpVl2sShH/qm+/5X/PEzI5/NGOmg15pX rJbW74RAcWO3rm3fh2k7mpC5x2njSVptBD+CQbnrEG3mdelD9XNaZ9SNSuxUF+10mrKr vBfMs2HDg+poIkwxFSMXiFtnOrJmlCn575ZoBxr8tSXXiIwGpOOT54AjXVlREiSeYwWP uBvdvU9+hMRriliVo7IucckQY5RbyzydAkaYmXAgJ5iOMHIdFut1WOtB6f5G1TPtKjMP Q2OzHRTuXbIlrBxoQfSUdwcBo7tvWgADxTeLmDQu027qvgXJ3Jnj0JnqmYiSeBrgQIqQ D7eA== X-Gm-Message-State: ALoCoQnbMR7NZcGynVmUglh/JPIgw1Liq0LH8qoVZTIeIkW5r0gRZw83K8fzHoARFycBajBnVOEv MIME-Version: 1.0 X-Received: by 10.66.242.17 with SMTP id wm17mr1140655pac.102.1380139167758; Wed, 25 Sep 2013 12:59:27 -0700 (PDT) Received: by 10.70.79.69 with HTTP; Wed, 25 Sep 2013 12:59:27 -0700 (PDT) In-Reply-To: <7174577A-E0A3-4111-8E4E-D466641A38CB@gmail.com> References: <7174577A-E0A3-4111-8E4E-D466641A38CB@gmail.com> Date: Wed, 25 Sep 2013 15:59:27 -0400 Message-ID: Subject: Re: Nodes not added to existing cluster From: "Laing, Michael" To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b111915d5d19504e73ab0f8 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b111915d5d19504e73ab0f8 Content-Type: text/plain; charset=UTF-8 Check your security groups to be sure you have appropriate access. If in a VPC check both IN and OUT; if using ACLs check those. On Wed, Sep 25, 2013 at 3:41 PM, Skye Book wrote: > Hi all, > > I have a three node cluster using the EC2 Multi-Region Snitch currently > operating only in US-EAST. On having a node go down this morning, I > started a new node with an identical configuration, except for the seed > list, the listen address and the rpc address. The new node comes up and > creates its own cluster rather than joining the pre-existing ring. I've > tried creating a node both *before* ad *after* using `nodetool remove` > for the bad node, each time with the same result. > > Does anyone have any suggestions for where to look that might put me on > the right track? > > Thanks, > -Skye > > --047d7b111915d5d19504e73ab0f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Check your security groups to be sure you have appropriate= access.

If in a VPC check both IN and OUT; if using ACL= s check those.


On Wed, Sep 25, 2013 at 3:41 PM, Skye Book <skye.book@gmail.com><= /span> wrote:
Hi all,

I have a thr= ee node cluster using the EC2 Multi-Region Snitch currently operating only = in US-EAST. =C2=A0On having a node go down this morning, I started a new no= de with an identical configuration, except for the seed list, the listen ad= dress and the rpc address. =C2=A0The new node comes up and creates its own = cluster rather than joining the pre-existing ring. =C2=A0I've tried cre= ating a node both before=C2=A0ad after=C2=A0using `nodetool r= emove` for the bad node, each time with the same result.

Does anyone have any suggestions for where to look that= might put me on the right track?

Thanks,
-Skye


--047d7b111915d5d19504e73ab0f8--