>
> I am seeing some unbalancing and I was worried because I have 256 vnodes
> Weird stuff is related to this post where I don't find a match between the
> load and du -sh * for the node 10.1.31.60 and I was trying to figure out
> the reason, if it was due to the number of vnodes.
Out of
ere's a
>>>> push for 4 in combination with allocate_tokens_for_keyspace from Jon
>>>> Haddad & co (based on a paper from Joe Lynch & Josh Snyder).
>>>>
>>>> If you're satisfied with the results from your own testing, go with 4
>>>>
at, Feb 1, 2020 at 5:17 AM Arvinder Dhillon
>>> wrote:
>>>
>>>> What is recommended vnodes now? I read 8 in later cassandra 3.x
>>>> Is the new recommendation 4 now even in version 3.x (asking for 3.11)?
>>>> Thanks
>>>>
>>>> On Fri,
Thanks Erick!
Best,
Sergio
On Sun, Feb 2, 2020, 10:07 PM Erick Ramirez wrote:
> If you are after more details about the trade-offs between different sized
>> token values, please see the discussion on the dev mailing list: "[Discuss]
>> num_tokens default in Cassandra 4.0
>>
Hi guys,
thanks a lot for useful tips. I obviously underestimated complexity of such
change.
Thanks again,
Maxim.
>
>
> If you are after more details about the trade-offs between different sized
> token values, please see the discussion on the dev mailing list: "[Discuss]
> num_tokens default in Cassandra 4.0
>
;> wrote:
>>>
>>>> What is recommended vnodes now? I read 8 in later cassandra 3.x
>>>> Is the new recommendation 4 now even in version 3.x (asking for 3.11)?
>>>> Thanks
>>>>
>>>> On Fri, Jan 31, 2
>>> Is the new recommendation 4 now even in version 3.x (asking for 3.11)?
>>> Thanks
>>>
>>> On Fri, Jan 31, 2020 at 9:49 AM Durity, Sean R <
>>> sean_r_dur...@homedepot.com> wrote:
>>>
>>>> These are good clarificat
.
>>>
>>>
>>>
>>> Sean Durity
>>>
>>>
>>>
>>> *From:* Anthony Grasso
>>> *Sent:* Thursday, January 30, 2020 7:25 PM
>>> *To:* user
>>> *Subject:* Re: [EXTERNAL] How to reduce vnodes without d
rom:* Anthony Grasso
>> *Sent:* Thursday, January 30, 2020 7:25 PM
>> *To:* user
>> *Subject:* Re: [EXTERNAL] How to reduce vnodes without downtime
>>
>>
>>
>> Hi Maxim,
>>
>>
>>
>> Basically what Sean suggested is the way to do this w
> *From:* Anthony Grasso
> *Sent:* Thursday, January 30, 2020 7:25 PM
> *To:* user
> *Subject:* Re: [EXTERNAL] How to reduce vnodes without downtime
>
>
>
> Hi Maxim,
>
>
>
> Basically what Sean suggested is the way to do this without downtime.
>
>
>
These are good clarifications and expansions.
Sean Durity
From: Anthony Grasso
Sent: Thursday, January 30, 2020 7:25 PM
To: user
Subject: Re: [EXTERNAL] How to reduce vnodes without downtime
Hi Maxim,
Basically what Sean suggested is the way to do this without downtime.
To clarify
Hi Maxim,
Basically what Sean suggested is the way to do this without downtime.
To clarify the, the *three* steps following the "Decommission each node in
the DC you are working on" step should be applied to *only* the
decommissioned nodes. So where it say "*all nodes*" or "*every node*" it
Your procedure won’t work very well. On the first node, if you switched to 4,
you would end up with only a tiny fraction of the data (because the other nodes
would still be at 256). I updated a large cluster (over 150 nodes – 2 DCs) to
smaller number of vnodes. The basic outline was this:
*
14 matches
Mail list logo