Instead of sstableloader consider dsbulk by datastax. On Fri, Jan 24, 2020 at 10:20 AM Reid Pinchback <rpinchb...@tripadvisor.com> wrote:
> Jon Haddad has previously made the case for num_tokens=4. His Accelerate > 2019 talk is available at: > > > > https://www.youtube.com/watch?v=swL7bCnolkU > > > > You might want to check that out. Also I think the amount of effort you > put into evening out the token distribution increases as vnode count > shrinks. The caveats are explored at: > > > > > https://thelastpickle.com/blog/2019/02/21/set-up-a-cluster-with-even-token-distribution.html > > > > > > *From: *Voytek Jarnot <voytek.jar...@gmail.com> > *Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org> > *Date: *Friday, January 24, 2020 at 10:39 AM > *To: *"user@cassandra.apache.org" <user@cassandra.apache.org> > *Subject: *sstableloader & num_tokens change > > > > *Message from External Sender* > > Running 3.11.x, 4 nodes RF=3, default 256 tokens; moving to a different 4 > node RF=3 cluster. > > > > I've read that 256 is not an optimal default num_tokens value, and that 32 > is likely a better option. > > > > We have the "opportunity" to switch, as we're migrating environments and > will likely be using sstableloader to do so. I'm curious if there are any > gotchas with using sstableloader to restore snapshots taken from 256-token > nodes into a cluster with 32-token nodes (otherwise same # of nodes and > same RF). > > > > Thanks in advance. >
