+1 on nodetool drain. I added that to our upgrade automation and it really helps with post-upgrade start-up time.
Sean Durity From: Erick Ramirez <erick.rami...@datastax.com> Sent: Wednesday, February 12, 2020 10:29 PM To: user@cassandra.apache.org Subject: Re: [EXTERNAL] Cassandra 3.11.X upgrades Yes to the steps. The only thing I would add is to run a nodetool drain before shutting C* down so all mutations are flushed to SSTables and there won't be any commit logs to replay on startup. Also, the usual "backup your cluster and configuration files" boilerplate applies. 😁 ________________________________ 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.
