A new node joining will receive (replication factor) streams for each token it has. If you use single token and RF=3, three hosts will send data at the same time (the data sent is the “losing” replica of the data based on the next/new topology that will exist after the node finishes bootstrapping m)
The actual steaming plan is calculated by the joining host, and it executed the streams concurrently. This is one of the reasons vnodes were created - many more streaming sources so you can add/remove nodes much faster This is also true of moves and decommissions, but not replacements on the same token. For the display order - I’m not sure what order you’re talking about being ascending (IP? Perhaps?), but nodetool ring I think displas in token order. > On Sep 12, 2022, at 12:05 AM, Marc Hoppins <marc.hopp...@eset.com> wrote: > > > It doesn’t. However, I like to know things. Thus, I wanted to know what > determines which nodes send their data in the order they do. > > Similarly, when the cluster was created, I added the seeds nodes in > numerically ascending order and then the other nodes in a similar fashion. So > why doesn’t nodetool display the status in that same order? > > From: Gil Ganz <gilg...@gmail.com> > Sent: Monday, September 12, 2022 8:50 AM > To: user@cassandra.apache.org > Subject: Re: Bootstrap data streaming order > > EXTERNAL > > I can understand why the number of nodes sending at once might be interesting > somehow, but why would the order of the nodes matter? > > On Fri, Sep 9, 2022 at 10:27 AM Marc Hoppins <marc.hopp...@eset.com> wrote: > Curiosity as to which data/node starts first, what determines the delivery > sequence, how many nodes send data at once and what determines that limit? > > The usual kind of questions. > > > > -----Original Message----- > From: Dinesh Joshi <djo...@apache.org> > Sent: Friday, September 9, 2022 9:14 AM > To: user@cassandra.apache.org > Subject: Re: Bootstrap data streaming order > > EXTERNAL > > > The data is requested asynchronously from peers. There is some logic to > select the peers however there isn’t a set order for data delivery. Why do > you ask? > > > > > On Sep 8, 2022, at 11:35 PM, Marc Hoppins <marc.hopp...@eset.com> wrote: > > > > Hulloa all, > > > > Can anyone shed light on the order which nodes will deliver data to a new > > node? Or point me toward a suitable chart/document? > > > > Does the new node accept data from each node in turn or simultaneously from > > multiple nodes? > > > > Thanks > > > > Marc
