You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Josh Elser (Jira)" <ji...@apache.org> on 2020/05/28 23:19:00 UTC

[jira] [Reopened] (PHOENIX-5922) IndexUpgradeTool should always re-enable tables on failure

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

Josh Elser reopened PHOENIX-5922:
---------------------------------

This breaks compilation on master: there are two StringUtils imports and redefines {{isWaitComplete}}.

I'll revert the offending commit and re-open this for Geoffrey to fix this.

> IndexUpgradeTool should always re-enable tables on failure
> ----------------------------------------------------------
>
>                 Key: PHOENIX-5922
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5922
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>             Fix For: 5.1.0, 4.16.0
>
>         Attachments: PHOENIX-5922-4.x.v1.patch
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> If an error occurs while doing an index upgrade, the IndexUpgradeTool will try to rollback the upgrade operations to leave the cluster in its initial state. However, if the rollback fails, it will give up. This can leave tables disabled for long periods until operators manually re-enable them.
> If rollback fails, the IndexUpgradeTool should always re-enable the affected tables at the HBase level.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)