[I] Upgrade from 4.0 to 4.1 may need to consider the fate table. [accumulo]

["keith-turner (via GitHub)" <gi...@apache.org>]

keith-turner opened a new issue, #4721:
URL: https://github.com/apache/accumulo/issues/4721

   Accumulo checks if any fate operation are present when upgrading and will refuse to upgrade if any are present.  In Accumulo 4.0 a new fate table was introduced.  Prior to Accumulo 4.0 fate operations were only stored in zookeeper.  After 4.0 fate operations are stored in zookeeper and the metadata table.  Eventually the upgrade code for 4.1 may need to check for fate operations in both of these places.  Currently the following code checks for fate operations in zookeeper only.
   
   https://github.com/apache/accumulo/blob/f6909cd7067cad575e70893f3c1d5f4c99cc5676/server/manager/src/main/java/org/apache/accumulo/manager/upgrade/UpgradeCoordinator.java#L313
   
   This issue covers a potential problem with unreleased code and therefore its possible it may become irrelevant depending on changes and could be closed if that happens.  Opening an issue now so that its not forgotten for 4.1 upgrade.
   
   
   


-- 
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.apache.org

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