Re: How does a node decide where each of its vnodes will be replicated to?

2021-11-08 Thread Tech Id
#x27;s just > hosts and ranges they own. > > On Mon, Nov 8, 2021 at 4:07 PM Tech Id wrote: > >> Thanks Jeff. >> >> One follow-up question please: Each node specifies num_tokens. >> So if there are 4 nodes and each specifies 256 tokens, then it means >> tog

Re: How does a node decide where each of its vnodes will be replicated to?

2021-11-08 Thread Tech Id
t; > The only thing that enforces any meaningful order or distribution here is > a rack-aware snitch, which will ensure that the RF copies of data land on > as many racks as possible (which is where it may skip some tokens, if > they're found to be on the same rack) > > > On Mon

Re: How does a node decide where each of its vnodes will be replicated to?

2021-11-08 Thread Tech Id
te > from "many" other sources (maybe a dozen, maybe a hundred). This was super > important before 4.0, because each replication stream was single threaded > by SENDER, so vnodes let you use more than 2-3 cores to re-replicate (in > 4.0, it's still single threaded, but

How does a node decide where each of its vnodes will be replicated to?

2021-11-08 Thread Tech Id
Hello, Going through https://docs.datastax.com/en/cassandra-oss/3.0/cassandra/architecture/archDataDistributeDistribute.html . But it is not clear how a node decides where each of its vnodes will be replicated to. As an example from the above page: 1. Why is vnode A present in nodes 1,2 and