n Durity – Staff Systems Engineer, Cassandra
>
>
>
> *From:* Erick Ramirez
> *Sent:* Friday, January 24, 2020 11:03 PM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] Re: sstableloader & num_tokens change
>
>
>
>
>
> If I may just loop this back
the original data size (or,
origin RF * target RF), until compaction can run.
Sean Durity – Staff Systems Engineer, Cassandra
From: Erick Ramirez
Sent: Friday, January 24, 2020 11:03 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: sstableloader & num_tokens change
If I may just loop this
Hello
Concerning the original question, I agreed with @eric_ramirez,
sstableloader is transparent for token allocation number.
just for info @voytek, check this post out
https://thelastpickle.com/blog/2019/02/21/set-up-a-cluster-with-even-token-distribution.html
You lay be interested to now if
On the subject of DSBulk, sstableloader is the tool of choice for this
scenario.
+1 to Sergio and I'm confirming that DSBulk is designed as a bulk loader
for CSV/JSON formats. Cheers!
> If I may just loop this back to the question at hand:
>
> I'm curious if there are any gotchas with using sstableloader to restore
> snapshots taken from 256-token nodes into a cluster with 32-token (or your
> preferred number of tokens) nodes (otherwise same # of nodes and same RF).
>
No,
t. Also I think the amount of effort
>>>> you put into evening out the token distribution increases as vnode count
>>>> shrinks. The caveats are explored at:
>>>>
>>>>
>>>>
>>>>
>>>> https://thelastpickle.c
;> https://thelastpickle.com/blog/2019/02/21/set-up-a-cluster-with-even-token-distribution.html
>>>
>>>
>>>
>>>
>>>
>>> *From: *Voytek Jarnot
>>> *Reply-To: *"user@cassandra.apache.org"
>>> *Date: *Friday, January 2
/21/set-up-a-cluster-with-even-token-distribution.html
>>>
>>>
>>>
>>>
>>>
>>> From: Voytek Jarnot
>>> Reply-To: "user@cassandra.apache.org"
>>> Date: Friday, January 24, 2020 at 10:39 AM
>>> To: "
en-token-distribution.html
>>
>>
>>
>>
>>
>> *From: *Voytek Jarnot
>> *Reply-To: *"user@cassandra.apache.org"
>> *Date: *Friday, January 24, 2020 at 10:39 AM
>> *To: *"user@cassandra.apache.org"
>> *Subject: *
gt;
>>
>>
>> https://thelastpickle.com/blog/2019/02/21/set-up-a-cluster-with-even-token-distribution.html
>>
>>
>>
>>
>>
>> *From: *Voytek Jarnot
>> *Reply-To: *"user@cassandra.apache.org"
>> *Date: *Friday, January 24, 2020 at
distribution.html
>
>
>
>
>
> *From: *Voytek Jarnot
> *Reply-To: *"user@cassandra.apache.org"
> *Date: *Friday, January 24, 2020 at 10:39 AM
> *To: *"user@cassandra.apache.org"
> *Subject: *sstableloader & num_tokens change
>
>
>
>
. The
caveats are explored at:
https://thelastpickle.com/blog/2019/02/21/set-up-a-cluster-with-even-token-distribution.html
From: Voytek Jarnot
Reply-To: "user@cassandra.apache.org"
Date: Friday, January 24, 2020 at 10:39 AM
To: "user@cassandra.apache.org"
Subject: sstabl
Running 3.11.x, 4 nodes RF=3, default 256 tokens; moving to a different 4
node RF=3 cluster.
I've read that 256 is not an optimal default num_tokens value, and that 32
is likely a better option.
We have the "opportunity" to switch, as we're migrating environments and
will likely be using
13 matches
Mail list logo
