Re: New token allocation and adding a new DC

I fixed the new allocation algorithm in non bootstrap case, https://issues.apache.org/jira/browse/CASSANDRA-13080?filter=-2, the fix is in 3.12+, but not in 3.0. On Wed, Jan 24, 2018 at 9:32 AM, Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On Thu, Jan 18, 2018 at 5:19 AM, kurt

Re: New token allocation and adding a new DC

On Thu, Jan 18, 2018 at 5:19 AM, kurt greaves wrote: > Didn't know that about auto_bootstrap and the algorithm. We should > probably fix that. Can you create a JIRA for that issue? > Will do. > Workaround for #2 would be to truncate system.available_ranges after >

Re: New token allocation and adding a new DC

Didn't know that about auto_bootstrap and the algorithm. We should probably fix that. Can you create a JIRA for that issue? Workaround for #2 would be to truncate system.available_ranges after "bootstrap". On 17 January 2018 at 17:26, Oleksandr Shulgin wrote: > On

Re: New token allocation and adding a new DC

Well, that's a shame... That part of the code has been changed in trunk and now it uses BootStrapper.getBootstrapTokens() instead of getRandomToken() when auto boostrap is disabled : https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L938 I

Re: New token allocation and adding a new DC

On Wed, Jan 17, 2018 at 4:21 AM, kurt greaves wrote: > I believe you are able to get away with just altering the keyspace to > include both DC's even before the DC exists, and then adding your nodes to > that new DC using the algorithm. Note you'll probably want to take the

Re: New token allocation and adding a new DC

I believe you are able to get away with just altering the keyspace to include both DC's even before the DC exists, and then adding your nodes to that new DC using the algorithm. Note you'll probably want to take the opportunity to reduce the number of vnodes to something reasonable. Based off

Re: New token allocation and adding a new DC

On Tue, Jan 16, 2018 at 4:16 PM, Alexander Dejanovski < a...@thelastpickle.com> wrote: > Hi Oleksandr, > > if bootstrap is disabled, it will only skip the streaming phase but will > still go through token allocation and thus should use the new algorithm. > The algorithm won't try to spread data

Re: New token allocation and adding a new DC

Hi Oleksandr, if bootstrap is disabled, it will only skip the streaming phase but will still go through token allocation and thus should use the new algorithm. The algorithm won't try to spread data based on size on disk but it will try to spread token ownership as evenly as possible. The