I don't like your cunning plan. Don't drop the system auth and distributed
keyspaces, instead just change them to NTS and then do your replacement for
each down node.
If you're actually using auth and worried about consistency I believe 3.11
has the feature to be able to exclude nodes during a re
No, that's not true.
On Sat., 22 Sep. 2018, 21:58 onmstester onmstester,
wrote:
>
> If you have problems with balance you can add new nodes using the
> algorithm and it'll balance out the cluster. You probably want to stick to
> 256 tokens though.
>
>
> I read somewhere (don't remember the ref)
Another question, Is there a management tool to do nodetool cleanup one by one
(wait until finish of cleaning up one node then start clean up for the next
node in cluster)? On Sat, 22 Sep 2018 16:02:17 +0330 onmstester onmstester
wrote I have a cunning plan (Baldrick wise) to solve
t
I have a cunning plan (Baldrick wise) to solve this problem: stop client
application run nodetool flush on all nodes to save memtables to disk stop
cassandra on all of the nodes rename original Cassandra data directory to
data-old start cassandra on all the nodes to create a fresh cluster includ
If you have problems with balance you can add new nodes using the algorithm and
it'll balance out the cluster. You probably want to stick to 256 tokens though.
I read somewhere (don't remember the ref) that all nodes of the cluster should
use the same algorithm, so if my cluster suffer from imba
>
> But one more question, should i use num_tokens : 8 (i would follow
> datastax recommendation) and allocate_tokens_for_local_replication_factor=3
> (which is max RF among my keyspaces) for new clusters which i'm going to
> setup?
16 is probably where it's at. Test beforehand though.
> Is the A
Thanks, Because all my clusters are already balanced, i won't change their
config But one more question, should i use num_tokens : 8 (i would follow
datastax recommendation) and allocate_tokens_for_local_replication_factor=3
(which is max RF among my keyspaces) for new clusters which i'm going t
If you have problems with balance you can add new nodes using the algorithm
and it'll balance out the cluster. You probably want to stick to 256 tokens
though.
To reduce your # tokens you'll have to do a DC migration (best way). Spin
up a new DC using the algorithm on the nodes and set a lower numb
I noticed that currently there is a discussion in ML with subject: changing
default token behavior for 4.0. Any recommendation to guys like me who already
have multiple clusters ( > 30 nodes in each cluster) with random partitioner
and num_tokens = 256? I should also add some nodes to existing c
