Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of arodrime@gmail.com designates
 209.85.217.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEDUwd1X8eZB8yK-CT9ijpY+iThqQnsQQYZ9dxBkApkkzNL5Yw@mail.gmail.com>
References: 
 <CAM+WaZiYFysdAYwDr+iH2fDCHm2aSbHSzV7gj26oicvB7r5BJg@mail.gmail.com>
 <CA+VSrLpB2ZEHCbE5rYCLEa0x-TDuJDLQ9ARPRwTbVcAXoe33Ng@mail.gmail.com>
 <CAEDUwd076ZA2kG1DxMeMPjQVPBc5B=fEj=kTT-M6cDOs17d73Q@mail.gmail.com>
 <CA+VSrLo5b4Q7Qg0AYn4ekZUdM_g88FRJ=CWGRf7qgsaq8oevvA@mail.gmail.com>
 <CAM+WaZhHuzJDzboFJ7Bhj7CnEYBrEgsdJ7afJ6f-tBJQfLB05w@mail.gmail.com>
 <CAEDUwd1X8eZB8yK-CT9ijpY+iThqQnsQQYZ9dxBkApkkzNL5Yw@mail.gmail.com>
From: Alain RODRIGUEZ <arodrime@gmail.com>
Date: Sat, 15 Feb 2014 18:31:06 +0100
Message-ID: 
 <CA+VSrLp9dmKtV7wHDPjgtyJOEi7TF9HW9yf5FPykj+3epXMPZg@mail.gmail.com>
Subject: Re: Bootstrap failure on C* 1.2.13
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=089e0115ff34c5b7f604f2754af0

--089e0115ff34c5b7f604f2754af0
Content-Type: text/plain; charset=ISO-8859-1

Hi Rob,

I don't understand how setting those "initial_token" might solve this
issue. Even more since we cannot set them before bootstrapping...

Plus, once those tokens set, we would have to modify them after any new
bootstrap / decommission. Which would also imply to run a rolling restart
for the new configuration (cassandra.yaml)  to be taken into account. This
is quite a heavy process to perform a "NOOP"...

What did I miss ?

Thanks for getting involved and trying to help anyway :).

Alain


2014-02-15 1:13 GMT+01:00 Robert Coli <rcoli@eventbrite.com>:

> On Fri, Feb 14, 2014 at 10:08 AM, Paulo Ricardo Motta Gomes <
> paulo.motta@chaordicsystems.com> wrote:
>
>> But in our case, our cluster was not using VNodes, so this workaround
>> will probably not work with VNodes, since you cannot specify the 256 tokens
>> from the old node.
>>
>
> Sure you can, in a comma delimited list. I plan to write a short blog post
> about this, but...
>
> I recommend that anyone using Cassandra, vnodes or not, always explicitly
> populate their initial_token line in cassandra.yaml. There are a number of
> cases where you will lose if you do not do so, and AFAICT no cases where
> you lose by doing so.
>
> If one is using vnodes and wants to do this, the process goes like :
>
> 1) set num_tokens to the desired number of vnodes
> 2) start node/bootstrap
> 3) use a one liner like jeffj's :
> "
> nodetool info -T | grep ^Token | awk '{ print $3 }' | tr \\n , | sed -e
> 's/,$/\n/'
> "
> to get a comma delimited list of the vnode tokens
> 4) insert this comma delimited list in initial_token, and comment out
> num_tokens (though it is a NOOP)
>
> =Rob
>

--089e0115ff34c5b7f604f2754af0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Rob,<div><br></div><div>I don&#39;t understand how sett=
ing those &quot;initial_token&quot; might solve this issue. Even more since=
 we cannot set them before bootstrapping...</div><div><br></div><div>Plus, =
once those tokens set, we would have to modify them after any new bootstrap=
 / decommission. Which would also imply to run a rolling restart for the ne=
w configuration (cassandra.yaml) =A0to be taken into account. This is quite=
 a heavy process to perform a &quot;NOOP&quot;...</div>

<div><br></div><div>What did I miss ?</div><div><br></div><div>Thanks for g=
etting involved and trying to help anyway :).</div><div><br></div><div>Alai=
n</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">

2014-02-15 1:13 GMT+01:00 Robert Coli <span dir=3D"ltr">&lt;<a href=3D"mail=
to:rcoli@eventbrite.com" target=3D"_blank">rcoli@eventbrite.com</a>&gt;</sp=
an>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
 class=3D"">On Fri, Feb 14, 2014 at 10:08 AM, Paulo Ricardo Motta Gomes <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:paulo.motta@chaordicsystems.com" targe=
t=3D"_blank">paulo.motta@chaordicsystems.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div>But in our case, our cluster was not=
 using VNodes, so this workaround will probably not work with VNodes, since=
 you cannot specify the 256 tokens from the old node.</div>


</div></blockquote><div><br></div></div><div>Sure you can, in a comma delim=
ited list. I plan to write a short blog post about this, but...</div><div><=
br></div><div>I recommend that anyone using Cassandra, vnodes or not, alway=
s explicitly populate their initial_token line in cassandra.yaml. There are=
 a number of cases where you will lose if you do not do so, and AFAICT no c=
ases where you lose by doing so.</div>


<div><br></div><div>If one is using vnodes and wants to do this, the proces=
s goes like :</div><div><br></div><div>1) set num_tokens to the desired num=
ber of vnodes</div><div>2) start node/bootstrap</div><div>3) use a one line=
r like jeffj&#39;s :</div>


<div>&quot;</div><div>nodetool info -T | grep ^Token | awk &#39;{ print $3 =
}&#39; | tr \\n , | sed -e &#39;s/,$/\n/&#39;<br></div><div>&quot;</div><di=
v>to get a comma delimited list of the vnode tokens</div><div>4) insert thi=
s comma delimited list in initial_token, and comment out num_tokens (though=
 it is a NOOP)</div>


<div><br></div><div>=3DRob</div></div></div></div>
</blockquote></div><br></div>

--089e0115ff34c5b7f604f2754af0--