[ACCUMULO-4496] Upgrade fails due to outstanding Fate operations, refers to nonexistant explaination of how to handle

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.7.2
• Labels: pull-request-available
• Assignee: Ed Coleman
• Reporter: John Vines
• Created: 11/Oct/16 19:40
• Updated: 16/Nov/18 12:43
• Resolved: 16/Nov/18 12:43

Description

2016-10-11 15:24:30,023 [server.Accumulo] FATAL: Problem verifying Fate readiness
org.apache.accumulo.core.client.AccumuloException: Aborting upgrade because there are outstanding FATE transactions from a previous Accumulo version. Please see the README document for instructions on w
hat to do under your previous version.
        at org.apache.accumulo.server.Accumulo.abortIfFateTransactions(Accumulo.java:317)
        at org.apache.accumulo.master.Master.upgradeZookeeper(Master.java:343)
        at org.apache.accumulo.master.Master.setMasterState(Master.java:283)
        at org.apache.accumulo.master.Master.getMasterLock(Master.java:1372)
        at org.apache.accumulo.master.Master.run(Master.java:1113)
        at com.sqrrl.analytics.server.admin.SqrrlMasterStart$MasterShim.run(SqrrlMasterStart.java:99)
        at java.lang.Thread.run(Thread.java:745)

However, there is no mention of this situation in README.md, nor in the UPGRADING.md. Not sure what the appropriate response is to this situation, but we should document it.

Issue Links

• is broken by: ACCUMULO-2519 FATE operation failed across upgrade
• links to: GitHub Pull Request #697