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 grea
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
> "bootstrap".
>
Thanks, that
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 Wed, Jan 17, 2018 at 4:21 AM, k
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 wa
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
> opportunity to reduc
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 memor
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 ba
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 problem
Hello,
We want to add a new rack to an existing cluster (a new Availability Zone
on AWS).
Currently we have 12 nodes in 2 racks with ~4 TB data per node. We also
want to have bigger number of smaller nodes. In order to minimize the
streaming we want to add a new DC which will span 3 racks and t
