Re: [Discuss] num_tokens default in Cassandra 4.0

2020-01-29 Thread Jeremy Hanna
The new default wouldn't be retroactively set for 3.x, but the same principles apply. The new algorithm is in 3.x as well as the simplification of the configuration. So no reason not to use the same configuration on 3.x. > On Jan 30, 2020, at 4:34 AM, Chen-Becker, Derek > wrote: > > Does th

Re: [Discuss] num_tokens default in Cassandra 4.0

2020-01-29 Thread Chen-Becker, Derek
Does the same guidance apply to 3.x clusters? I read through the JIRA ticket linked below, along with tickets that it links to, but it's not clear that the new allocation algorithm is available in 3.x or if there are other reasons that this would be problematic. Thanks, Derek On 1/29/20, 9:5

Re: [Discuss] num_tokens default in Cassandra 4.0

2020-01-29 Thread Jon Haddad
Ive put a lot of my previous clients on 4 tokens, all of which have resulted in a major improvement. I wouldn't use any more than 4 except under some pretty unusual circumstances. Jon On Wed, Jan 29, 2020, 11:18 AM Ben Bromhead wrote: > +1 to reducing the number of tokens as low as possible fo

Re: [Discuss] num_tokens default in Cassandra 4.0

2020-01-29 Thread Ben Bromhead
+1 to reducing the number of tokens as low as possible for availability issues. 4 lgtm On Wed, Jan 29, 2020 at 1:14 AM Dinesh Joshi wrote: > Thanks for restarting this discussion Jeremy. I personally think 4 is a > good number as a default. I think whatever we pick, we should have enough > docum