Keep using whatever settings you've been using. I'd still use allocate tokens for keyspace but it probably won't make much of a difference with 256 tokens.
On Sat, Sep 8, 2018 at 10:40 AM onmstester onmstester <onmstes...@zoho.com> wrote: > Thanks Jon, > But i never concerned about num_tokens config before, because no official > cluster setup documents (on datastax: > https://docs.datastax.com/en/cassandra/3.0/cassandra/initialize/initSingleDS.html > or other blogs) warned us-beginners to be concerned about it. > I always setup my clusters with nodes having same hardware spec > (homogeneous) and num_tokens = 256, and data seems to be evenly > distributed, at least nodetool status report it that way + killing any > node, i still got all of my data and application was working, So i assumed > data perfectly and evenly distributed among nodes. > So could you please explain more why should i run that python command and > config allocate_tokens_for_keyspace? i only have one keyspace per cluster. > Im using Network replication strategy, and a rack-aware topology config. > > Sent using Zoho Mail <https://www.zoho.com/mail/> > > > ---- On Sat, 08 Sep 2018 17:17:10 +0430 *Jonathan Haddad > <j...@jonhaddad.com <j...@jonhaddad.com>>* wrote ---- > > 256 tokens is a pretty terrible default setting especially post 3.0. I > recommend folks use 4 tokens for new clusters, with some caveats. > > When you fire up a cluster, there's no way to make the initial tokens be > distributed evenly, you'll get random ones. You'll want to set them > explicitly using: > > python -c 'print( [str(((2**64 / 4) * i) - 2**63) for i in range(4)])' > > > After you fire up the first seed, create a keyspace using RF=3 (or > whatever you're planning on using) and set allocate_tokens_for_keyspace to > that keyspace in your config, and join the rest of the nodes. That gives > even distribution. > > On Sat, Sep 8, 2018 at 1:40 AM onmstester onmstester <onmstes...@zoho.com> > wrote: > > > > -- > Jon Haddad > http://www.rustyrazorblade.com > twitter: rustyrazorblade > > > > > -- Jon Haddad http://www.rustyrazorblade.com twitter: rustyrazorblade
