You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ctubbsii (via GitHub)" <gi...@apache.org> on 2025/04/01 00:09:06 UTC

Re: [PR] Modified ZooZap to add '-prepare-for-upgrade` option [accumulo]

ctubbsii commented on PR #5438:
URL: https://github.com/apache/accumulo/pull/5438#issuecomment-2767688508

   Can we get an updated description of this PR? It links to another PR that is much bigger, but I haven't reviewed yet. Based on previous conversations, I *think* this is supposed to just kill locks in ZK, and then add a flag that the AbstractServer base class looks for, in order to prevent starting up anything if the flag is seen.
   
   However, I have a couple of concerns/questions:
   
   1. What if a user starts up 2.1.3 services? 2.1.x should be forwards/backwards compatible, so this should be fine. Now, we cannot trust that this flag in ZK actually prevented any services from holding locks.
   2. What if the user runs this to upgrade to 2.1.5? Is there enough information in the node in the new node in ZK to allow that as an upgrade path? What about if they jump straight to 2.1.6? Those should have the same data versions as 2.1.4, but will they be prevented from starting up?


-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org