I would only run the clean-up (on all nodes) after all new nodes are added. I would also look at increasing RF to 3 (and running repair) once there are plenty of nodes. (This is assuming that availability matters and that your queries use QUORUM or LOCAL_QUORUM for consistency level.
Longer term, I agree with Oleksandr, the recommendation for number of vnodes is now much smaller than 256. I am using 8 or 16. Sean Durity From: Oleksandr Shulgin <oleksandr.shul...@zalando.de> Sent: Monday, September 03, 2018 10:02 AM To: User <user@cassandra.apache.org> Subject: [EXTERNAL] Re: adding multiple node to a cluster, cleanup and num_tokens On Mon, Sep 3, 2018 at 12:19 PM onmstester onmstester <onmstes...@zoho.com<mailto:onmstes...@zoho.com>> wrote: What i have understood from this part of document is that, when i already have node A,B and C in cluster there would be some old data on A,B,C after new node D joined the cluster completely which is data streamed to D, then if i add node E to the cluster immediately, the old data on A,B,C would be also moved between nodes everytime? Potentially, when you add node E it takes ownership of some of the data that D has. So you have to run cleanup on all (except the very last node you add) in the end. It still makes sense to do this once, not after every single node you add. -- Alex ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
