accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4496) Upgrade fails due to outstanding Fate operations, refers to nonexistant explaination of how to handle
Date Tue, 11 Oct 2016 20:15:20 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566452#comment-15566452
] 

Josh Elser commented on ACCUMULO-4496:
--------------------------------------

Hah! Funny, I think I was just talking to [~busbey] about this today IRL.

He noticed that the completed, but not reaped, FATE transactions could cause an upgrade to
fail. Instead of trying to parse the FATE op and ignore COMPLETE operations, we just fail
if any are found. He suggested that we could attempt to parse the FATE op and ignore those
which are completed, failing only when there is an unparse-able or non-completed one.

This sounded like a good idea to me.

FYI [~kturner]

> 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
>
> {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
(v6.3.4#6332)

Mime
View raw message