ddanielr opened a new issue, #5279: URL: https://github.com/apache/accumulo/issues/5279
**Is your feature request related to a problem? Please describe.** In our current upgrade code, we perform the pre-upgrade validation as part of the new accumulo version. If there is an issue like FATE transactions existing, we advise users to bring back up tservers and use the shell to remove them. However, at that point the deployed software has been changed to the new accumulo version and could fail to properly remove the conflicting data. To move forward with the upgrade, the user need to go backwards in their upgrade process and revert their software deployment steps in order to remove the FATEs. **Describe the solution you'd like** Add a utility that runs pre-validation code after a system is shutdown. It could remove existing fates, then adds a flag in ZK (e.g. UPGRADE_PREP) that prevents any new process from doing any transaction operation (i.e. FATE). This flag is then removed by the manager process when first running the new upgrade code. This allows a user to put the system into a "Upgrade ready" state while not requiring the user to perform software deployment steps that, most likely, would need to be immediately reverted. This utility could also dump configs as part of prepping for an upgrade if so desired. **Describe alternatives you've considered** We could just provide a flag on the existing fate command to delete and remove all current fates. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
