Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
References: 
 <CAEQiCCVC3AygJAiPOVJJ4uG2wYQbgihEkbA_1BoBNUYc1uKaLw@mail.gmail.com>
In-Reply-To: 
 <CAEQiCCVC3AygJAiPOVJJ4uG2wYQbgihEkbA_1BoBNUYc1uKaLw@mail.gmail.com>
From: Ben Bromhead <ben@instaclustr.com>
Date: Wed, 03 Feb 2016 20:10:51 +0000
Message-ID: 
 <CAA=6J0-sTXLhsqykUrRFM+gWRkf_qNS13N4JBTqWsS5Q7Ag-uQ@mail.gmail.com>
Subject: Re: Any tips on how to track down why Cassandra won't cluster?
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=089e011602a88a4bcf052ae33708

--089e011602a88a4bcf052ae33708
Content-Type: text/plain; charset=UTF-8

Check network connectivity. If you are using public addresses as the
broadcast, make sure you can telnet from one node to the other nodes public
address using the internode port.

Last time I looked into something like this, for some reason if you only
add a security group id to the allowed traffic in a security group you
still need to add public IP addresses for each node in a security groups
allowed inbound traffic as well.

On Wed, 3 Feb 2016 at 11:49 Richard L. Burton III <mrburton@gmail.com>
wrote:

> I'm deploying 2 nodes at the moment using cassandra-dse on Amazon. I
> configured it to use EC2Snitch and configured rackdc to use us-east with
> rack "1".
>
> The second node points to the first node as the seed e.g., "seeds":
> ["54.*.*.*"] and all of the ports are open.
>
> Any suggestions on how to track down what might trigger this problem? I'm
> not receiving any exceptions.
>
>
> --
> -Richard L. Burton III
> @rburton
>
-- 
Ben Bromhead
CTO | Instaclustr
+1 650 284 9692

--089e011602a88a4bcf052ae33708
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Check network connectivity. If you are using public addres=
ses as the broadcast, make sure you can telnet from one node to the other n=
odes public address using the internode port.<div><br></div><div>Last time =
I looked into something like this, for some reason if you only add a securi=
ty group id to the allowed traffic in a security group you still need to ad=
d public IP addresses for each node in a security groups allowed inbound tr=
affic as well.=C2=A0</div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr">On Wed, 3 Feb 2016 at 11:49 Richard L. Burton III &lt;<a href=3D"mailt=
o:mrburton@gmail.com">mrburton@gmail.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div dir=3D"ltr">I&#39;m deploying 2 nodes at the mome=
nt using=C2=A0cassandra-dse on Amazon. I configured it to use EC2Snitch and=
 configured rackdc to use us-east with rack &quot;1&quot;.<div><br></div><d=
iv>The second node points to the first node as the seed e.g., &quot;seeds&q=
uot;: [&quot;54.*.*.*&quot;] and all of the ports are open.</div><div><br><=
/div><div>Any suggestions on how to track down what might trigger this prob=
lem? I&#39;m not receiving any exceptions.</div></div><div dir=3D"ltr"><div=
><br clear=3D"all"><div><br></div>-- <br><div><div dir=3D"ltr">-Richard L. =
Burton III<div>@rburton</div></div></div>
</div></div></blockquote></div><div dir=3D"ltr">-- <br></div><div dir=3D"lt=
r"><div>Ben Bromhead</div>CTO | Instaclustr<div>+1 650 284 9692</div></div>

--089e011602a88a4bcf052ae33708--