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

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-4496.
-----------------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 2.0.0)

Resolved in https://github.com/apache/accumulo/pull/697

> Upgrade fails due to outstanding Fate operations, refers to nonexistant explaination of how to handle
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4496
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4496
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.7.2
>            Reporter: John Vines
>            Assignee: Ed Coleman
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> {code}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){code}
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)