It mostly seems so. The thing that bugs me is that some things acted like they weren't joining as a normal new node. For example, I forgot to mention until I read your comment, that the instances showed as UN (up, normal) instead of UJ (up, joining) while they were apparently bootstrapping.
Thanks for the assurance. I'm thinking (hoping) that we're good. On Thu, Oct 20, 2016 at 11:24 PM, kurt Greaves <k...@instaclustr.com> wrote: > > On 20 October 2016 at 20:58, Branton Davis <branton.da...@spanning.com> > wrote: > >> Would they have taken on the token ranges of the original nodes or acted >> like new nodes and got new token ranges? If the latter, is it possible >> that any data moved from the healthy nodes to the "new" nodes or >> would restarting them with the original data (and repairing) put >> the cluster's token ranges back into a normal state? > > > It sounds like you stopped them before they completed joining. So you > should have nothing to worry about. If not, you will see them marked as DN > from other nodes in the cluster. If you did, they wouldn't have assumed the > token ranges and you shouldn't have any issues. > > You can just copy the original data back (including system tables) and > they should assume their own ranges again, and then you can repair to fix > any missing replicas. > > Kurt Greaves > k...@instaclustr.com > www.instaclustr.com >
