That's assuming your data is perfectly consistent, which is unlikely. Typically that strategy is a bad idea and you should avoid it.
On Thu., 19 Apr. 2018, 07:00 Richard Gray, <richard.g...@smxemail.com> wrote: > On 2018-04-18 21:28, kurt greaves wrote: > > replacing. Simply removing and adding back a new node without replace > > address will end up with the new node having different tokens, which > > would mean data loss in the use case you described. > > If you have replication factor N > 1, you haven't necessarily lost data > unless you've swapped out N or more nodes (without using > replace_address). If you've swapped out fewer than N nodes, you should > still be able to restore consistency by running a repair. > > -- > Richard Gray > > _____________________________________________________________________________ > > This email has been filtered by SMX. For more info visit > http://smxemail.com > > _____________________________________________________________________________ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > >
