Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: <CAPbVhuOozGoL_-jop3B_tSij2AWgEjQnENntZO43qTeW8F1bRA@mail.gmail.com>
References: <CAM3v5FsgSkantZT6n1x0v6dWA72LtTM=orOG8bzDcx3F82wucQ@mail.gmail.com>
 <CAPbVhuOozGoL_-jop3B_tSij2AWgEjQnENntZO43qTeW8F1bRA@mail.gmail.com>
From: shalom sagges <shalomsagges@gmail.com>
Date: Tue, 24 Oct 2017 15:27:33 +0300
Message-ID: <CAM3v5FvYF7A-6cqdEdQAA=Wo5ZMqaWdVCB=yJuSxXyT+ahx4xA@mail.gmail.com>
Subject: Re: Adding a New Node
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary="001a113da8284425ba055c4a1007"
archived-at: Tue, 24 Oct 2017 12:27:47 -0000

--001a113da8284425ba055c4a1007
Content-Type: text/plain; charset="UTF-8"

Thanks Kurt!

That sorted things in my head. Much appreciated!


On Tue, Oct 24, 2017 at 12:29 PM, kurt greaves <kurt@instaclustr.com> wrote:

> Your node shouldn't show up in DC1 in nodetool status from the other
> nodes, this implies a configuration problem. Sounds like you haven't added
> the new node to all the existing nodes cassandra-topology.properties file.
> You don't need to do a rolling restart with PropertyFileSnitch, it should
> reload the cassandra-topology.properties file automatically every 5 seconds.
>
> With GPFS each node only needs to know about its own topology settings in
> cassandra-rackdc.properties, so the problem you point out in 2 goes away,
> as when adding a node you only need to specify its configuration and that
> will be propagated to the rest of the cluster through gossip.
>
> On 24 October 2017 at 07:13, shalom sagges <shalomsagges@gmail.com> wrote:
>
>> Hi Everyone,
>>
>> I have 2 DCs (v2.0.14) with the following topology.properties:
>>
>> DC1:
>> xxx11=DC1:RAC1
>> xxx12=DC1:RAC1
>> xxx13=DC1:RAC1
>> xxx14=DC1:RAC1
>> xxx15=DC1:RAC1
>>
>>
>> DC2:
>> yyy11=DC2:RAC1
>> yyy12=DC2:RAC1
>> yyy13=DC2:RAC1
>> yyy14=DC2:RAC1
>> yyy15=DC2:RAC1
>>
>>
>> # default for unknown nodes
>> default=DC1:RAC1
>>
>> Now let's say that I want to add a new node yyy16 to DC2, and I've added
>> yyy16 to the topology properties file only on that specific node.
>>
>> What I saw is that during bootstrap, the new node is receiving data only
>> from DC2 nodes (which is what I want), but nodetool status on other nodes
>> shows that it was joining to DC1 (which is the default DC for unknown
>> nodes).
>>
>> So I have a few questions on this matter:
>>
>> 1) What are the implications of such a bootstrap, where the joining node
>> actually gets data from nodes in the right DC, but all nodes see it in the
>> default DC when running nodetool status?
>>
>> 2) I know that I must change the topology.properties file on all nodes to
>> be the same. If I do that, do I need to perform a rolling restart on all of
>> the cluster before each bootstrap (which is a real pain for large clusters)?
>>
>> 3) Regarding the Snitch, the docs say that the recommended snitch in
>> Production is the GossipingPropertyFileSnitch with
>> cassandra-rackdc.properties file.
>> What's the difference between the GossipingPropertyFileSnitchand and the
>> PropertyFileSnitch?
>> I currently use PropertyFileSnitch and cassandra-topology.properties.
>>
>>
>> Thanks!
>>
>>
>>
>>
>>
>>
>

--001a113da8284425ba055c4a1007
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks Kurt!<br><br></div>That sorted things in my he=
ad. Much appreciated!<br><br><br></div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Tue, Oct 24, 2017 at 12:29 PM, kurt greaves <span =
dir=3D"ltr">&lt;<a href=3D"mailto:kurt@instaclustr.com" target=3D"_blank">k=
urt@instaclustr.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"ltr"><div>Your node shouldn&#39;t show up in DC1 in nodetool s=
tatus from the other nodes, this implies a configuration problem. Sounds li=
ke you haven&#39;t added the new node to all the existing nodes cassandra-t=
opology.properties file. You don&#39;t need to do a rolling restart with Pr=
opertyFileSnitch, it should reload the cassandra-topology.properties file a=
utomatically every 5 seconds.</div><div><br></div><div>With GPFS each node =
only needs to know about its own topology settings in cassandra-rackdc.prop=
erties, so the problem you point out in 2 goes away, as when adding a node =
you only need to specify its configuration and that will be propagated to t=
he rest of the cluster through gossip.=C2=A0<br></div></div><div class=3D"H=
OEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On 24 October 2017 at 07:13, shalom sagges <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:shalomsagges@gmail.com" target=3D"_blank">shalomsagges@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"l=
tr"><div><div><div><div>Hi Everyone, <br><br></div>I have 2 DCs (v2.0.14) w=
ith the following topology.properties:<br><br>DC1:<br>xxx11=3DDC1:RAC1<br>x=
xx12=3DDC1:RAC1<br>xxx13=3DDC1:RAC1<br>xxx14=3DDC1:RAC1<br>xxx15=3DDC1:RAC1=
<br><br><br>DC2:<br>yyy11=3DDC2:RAC1<br>yyy12=3DDC2:RAC1<br>yyy13=3DDC2:RAC=
1<br>yyy14=3DDC2:RAC1<br>yyy15=3DDC2:RAC1<br><br><br># default for unknown =
nodes<br>default=3DDC1:RAC1<br><br></div>Now let&#39;s say that I want to a=
dd a new node yyy16 to DC2, and I&#39;ve added yyy16 to the topology proper=
ties file only on that specific node. <br></div><div><br></div>What I saw i=
s that during bootstrap, the new node is receiving data only from DC2 nodes=
 (which is what I want), but nodetool status on other nodes shows that it w=
as joining to DC1 (which is the default DC for unknown nodes). <br></div><d=
iv><br></div><div>So I have a few questions on this matter:</div><div><br><=
/div><div>1) What are the implications of such a bootstrap, where the joini=
ng node actually gets data from nodes in the right DC, but all nodes see it=
 in the default DC when running nodetool status?</div><div><br></div><div>2=
) I know that I must change the topology.properties file on all nodes to be=
 the same. If I do that, do I need to perform a rolling restart on all of t=
he cluster before each bootstrap (which is a real pain for large clusters)?=
</div><div><br></div><div>3) Regarding the Snitch, the docs say that the re=
commended snitch in Production is the GossipingPropertyFileSnitch with cass=
andra-rackdc.properties file. <br></div><div></div><div>What&#39;s the diff=
erence between the GossipingPropertyFileSnitchand and the PropertyFileSnitc=
h?</div><div>I currently use PropertyFileSnitch and cassandra-topology.prop=
erties. <br></div><div><br></div><div><br></div><div>Thanks!</div><div><br>=
</div><div><br></div><div><div><br><br><br></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a113da8284425ba055c4a1007--