Thanks for the pointers Kurt! I did increase the RF to N so that would not have been the issue. DC migration is also a problem since I am using the Google Cloud Snitch. So I'd have to take down the whole DC and restart anew (which would mess with my clients as they only connect to their local DC).
As I said this was a small issue here - we only were seeing the issue for 5 minutes. But considering how miniscule the amount of data to replicate was (400 rows with a total of 500kb) I am a bit worried on how to do this once loads increases. greetings Daniel On Wed, 2 Aug 2017 at 11:50 kurt greaves <k...@instaclustr.com> wrote: > If you want to change RF on a live system your best bet is through DC > migration (add another DC with the desired # of nodes and RF), and migrate > your clients to use that DC. There is a way to boot a node and not join the > ring, however I don't think it will work for new nodes (have not > confirmed), also increasing RF in this way would only not be completely > catastrophic if you were increasing RF to N (num nodes). >
