Re: Recommended num_tokens setting for small cluster

Hi for best performance you can start form node that has lower disk capacity and set it to 256 and for other nods use proportion to this node to find num of tokens. > On Shahrivar 9, 1397 AP, at 10:40, Max C. wrote: > > Jeff/Kurt/Alex — thanks so much for your feedback on this issue, and than

Re: Recommended num_tokens setting for small cluster

Jeff/Kurt/Alex — thanks so much for your feedback on this issue, and thanks for all of the help you guys have lent to people on this list over the years. :-) - Max > On Aug 29, 2018, at 11:38 pm, Oleksandr Shulgin > wrote: > > On Thu, Aug 30, 2018 at 12:05

Re: Recommended num_tokens setting for small cluster

On Thu, Aug 30, 2018 at 12:05 AM kurt greaves wrote: > For 10 nodes you probably want to use between 32 and 64. Make sure you use > the token allocation algorithm by specifying allocate_tokens_for_keyspace > We are using 16 tokens with 30 nodes on Cassandra 3.0. And yes, we have used allocate_t

Re: Recommended num_tokens setting for small cluster

For 10 nodes you probably want to use between 32 and 64. Make sure you use the token allocation algorithm by specifying allocate_tokens_for_keyspace On Thu., 30 Aug. 2018, 04:40 Jeff Jirsa, wrote: > 3.0 has a (optional?) feature to guarantee better distribution, and the > blog focuses on 2.2. >

Re: Recommended num_tokens setting for small cluster

3.0 has a (optional?) feature to guarantee better distribution, and the blog focuses on 2.2. Using fewer will minimize your risk of unavailability if any two hosts fail. -- Jeff Jirsa > On Aug 29, 2018, at 11:18 AM, Max C. wrote: > > Hello Everyone, > > Datastax recommends num_tokens = 8

Recommended num_tokens setting for small cluster

Hello Everyone, Datastax recommends num_tokens = 8 as a sensible default, rather than num_tokens = 256: https://docs.datastax.com/en/dse/5.1/dse-dev/datastax_enterprise/config/configVnodes.html … but t