RE: When Replacing a Node, How to Force a Consistent Bootstrap

2017-12-14 Thread Fd Habash
“ … but it's better to repair before and after if possible …” After, I simply run ‘nodetool repair –full’ on the replaced node. But before bootstrapping, if my cluster is distributed over 3 AZ’s, what do I repair? The entire other AZ’s? As one pointed out earlier, I can use ‘nodetool repair

RE: When Replacing a Node, How to Force a Consistent Bootstrap

2017-12-07 Thread Fd Habash
Thank you. How do I identify what other 2 nodes the former downed node replicated with? A replica set of 3 nodes A,B,C. Now, C has been terminated by AWS and is gone. Using the getendpoints assumes knowing a partition key value, but how do you even know what key to use? If there is a way to

Re: When Replacing a Node, How to Force a Consistent Bootstrap

2017-12-06 Thread kurt greaves
That's also an option but it's better to repair before and after if possible, if you don't repair beforehand you could end up missing some replicas until you repair after replacement, which could cause queries to return old/no data. Alternatively you could use ALL after replacing until the repair