You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Abhishek Singh Chouhan (Jira)" <ji...@apache.org> on 2020/06/05 05:23:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17126404#comment-17126404 ]
Abhishek Singh Chouhan commented on PHOENIX-5922:
-------------------------------------------------
[~gjacoby] A lot of precommit builds are aborting due to timeout, which is due to ParameterizedIndexUpgradeToolIT taking hours. Might be related to 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, PHOENIX-5922.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)