You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Mikhail Tsaplin <ts...@gmail.com> on 2018/03/08 11:09:58 UTC
Joining a cluster of nodes having multi valued initial_token parameters.
Hi,
I have a three node Cassandra cluster. Every node has initial_token
configuration parameter holding 256 tokens (looks like randomly
distributed). Now I have to add a fourth node. How could this be done?
PS.
Part of 'nodetool ring' output:
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-9205713283623500871
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-9192600956436545064
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-9189716240291717028
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-9176926431738979228
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-9165630329819435511
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-9131551322440793355
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-9085388549311448831
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-9077207130395766317
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-9061985382069345107
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-9056198271354592444
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-9043836508228627538
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-9014546164926268476
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8999948589107196010
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8975177269384421913
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8962289086769554506
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8975177269384421913
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8962289086769554506
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8953044682536974952
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8940303487395739838
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8932387676686616983
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8873109928322486075
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8865051362079782706
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8850179834054364371
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8829204422899132900
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8811000390052357789
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8786230694679663375
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8780652960415374467
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8764859109842746091
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8708700917906013815
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8693842389745975524
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8691834500817677507
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8678838469759345534
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8678185112109259638
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8588096283891642821
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8543483742622219334
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8490181966113387801
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8472605976529571179
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8424232155005744046
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8418821255394085837
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8351686364997722614
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8304042975009246920
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8275989122825748469
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8266684813696332376
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8249604834221262904
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8215356554591051668
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8185570155849318773
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8145020513310251737
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-8143432072864714436
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8092890658287786359
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8091932066709768375
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8072686015919353947
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8061756074468786955
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-8008967478448783673
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-8005513914038663113
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7983999640083064016
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7970446522216605710
192.168.1.125 rack1 Up Normal 2.54 TB 63.37%
-7966821094333580232
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7958041291006467513
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7954556181877538027
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7918439624031428293
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7871822142254502388
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7871623256828275065
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-7850671760027858550
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7826460674763710952
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-7823501329051165286
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-7774882275866624692
192.168.1.123 rack1 Up Normal 2.84 TB 70.53%
-7711728402123163089
192.168.1.126 rack1 Up Normal 2.66 TB 66.10%
-7774882275866624692
Re: Joining a cluster of nodes having multi valued initial_token parameters.
Posted by Mikhail Tsaplin <ts...@gmail.com>.
I suspect that cluster was created by recovering from a snapshot.
PS.
I asked a related question on this mailing list. Please check
subject: Removing initial_token parameter.
2018-03-08 20:02 GMT+07:00 Oleksandr Shulgin <ol...@zalando.de>:
> On Thu, Mar 8, 2018 at 1:41 PM, Mikhail Tsaplin <ts...@gmail.com>
> wrote:
>
>> Thank you for the answer, are you sure that it at least safe?
>>
>
> I would test in a lab first of course, but I don't see why it should be a
> problem. I wonder more why did you have tokens listed explicitly on the
> existing nodes if they are randomly generated?
>
>
>> As I understand I will have to specify auto_bootstrap=true too?
>>
>
> Sure. Set it to true or remove from configuration file altogether.
>
> --
> Alex
>
>
Re: Joining a cluster of nodes having multi valued initial_token parameters.
Posted by Oleksandr Shulgin <ol...@zalando.de>.
On Thu, Mar 8, 2018 at 1:41 PM, Mikhail Tsaplin <ts...@gmail.com> wrote:
> Thank you for the answer, are you sure that it at least safe?
>
I would test in a lab first of course, but I don't see why it should be a
problem. I wonder more why did you have tokens listed explicitly on the
existing nodes if they are randomly generated?
> As I understand I will have to specify auto_bootstrap=true too?
>
Sure. Set it to true or remove from configuration file altogether.
--
Alex
Re: Joining a cluster of nodes having multi valued initial_token parameters.
Posted by Mikhail Tsaplin <ts...@gmail.com>.
Thank you for the answer, are you sure that it at least safe?
As I understand I will have to specify auto_bootstrap=true too?
2018-03-08 18:16 GMT+07:00 Oleksandr Shulgin <ol...@zalando.de>:
> On Thu, Mar 8, 2018 at 12:09 PM, Mikhail Tsaplin <ts...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I have a three node Cassandra cluster. Every node has initial_token
>> configuration parameter holding 256 tokens (looks like randomly
>> distributed). Now I have to add a fourth node. How could this be done?
>>
>
> I think the easiest and safest way would be to use num_tokens=256 and not
> specifying the initial_token for the new node. This way it is supposed to
> generate tokens itself, taking into account the existing tokens in the ring
> to avoid clashes.
>
> --
> Alex
>
>
Re: Joining a cluster of nodes having multi valued initial_token parameters.
Posted by Oleksandr Shulgin <ol...@zalando.de>.
On Thu, Mar 8, 2018 at 12:09 PM, Mikhail Tsaplin <ts...@gmail.com> wrote:
> Hi,
>
> I have a three node Cassandra cluster. Every node has initial_token
> configuration parameter holding 256 tokens (looks like randomly
> distributed). Now I have to add a fourth node. How could this be done?
>
I think the easiest and safest way would be to use num_tokens=256 and not
specifying the initial_token for the new node. This way it is supposed to
generate tokens itself, taking into account the existing tokens in the ring
to avoid clashes.
--
Alex