Re: Configuration for new(expanding) cluster and new admins.

2022-06-20 Thread Jeff Jirsa
ng in a >> heterogenous storage configuration. In these cases how would it affect >> efficiency if the token figure were the same across all nodes? >> >> >> >> From: Elliott Sims >> Sent: Thursday, June 16, 2022 12:24 AM >> To: user@cassandra.apache.org >

Re: Configuration for new(expanding) cluster and new admins.

2022-06-20 Thread Elliott Sims
fect > efficiency if the token figure were the same across all nodes? > > > > *From:* Elliott Sims > *Sent:* Thursday, June 16, 2022 12:24 AM > *To:* user@cassandra.apache.org > *Subject:* Re: Configuration for new(expanding) cluster and new admins. > > > > EXTERNAL >

RE: Configuration for new(expanding) cluster and new admins.

2022-06-16 Thread Durity, Sean R
I have run clusters with different disk size nodes by using different number of num_tokens. I used the basic math of just increasing the num_tokens by the same percentage as change in disk size. (So, if my "normal" node was 8 tokens, one with double the disk space would be 16.) One thing to wat

RE: Configuration for new(expanding) cluster and new admins.

2022-06-15 Thread Marc Hoppins
ncy if the token figure were the same across all nodes? From: Elliott Sims Sent: Thursday, June 16, 2022 12:24 AM To: user@cassandra.apache.org Subject: Re: Configuration for new(expanding) cluster and new admins. EXTERNAL If you set a different num_tokens value for new hosts (the value should ne

Re: Configuration for new(expanding) cluster and new admins.

2022-06-15 Thread Elliott Sims
If you set a different num_tokens value for new hosts (the value should never be changed on an existing host), the amount of data moved to that host will be proportional to the num_tokens value. So, if the new hosts are set to 32 when they're added to the cluster, those hosts will get twice as muc

Re: Configuration for new(expanding) cluster and new admins.

2022-06-15 Thread Jeff Jirsa
You shouldn't need to change num_tokens at all. num_tokens helps you pretend your cluster is a bigger than it is and randomly selects tokens for you so that your data is approximately evenly distributed. As you add more hosts, it should balance out automatically. The alternative to num_tokens is