You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2020/05/27 23:26:00 UTC

[jira] [Updated] (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 ]

Geoffrey Jacoby updated PHOENIX-5922:
-------------------------------------
    Attachment: PHOENIX-5922-4.x.v1.patch

> 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
>         Attachments: PHOENIX-5922-4.x.v1.patch
>
>          Time Spent: 20m
>  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)