[
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642569#comment-16642569
]
Hudson commented on HBASE-21271:
--------------------------------
Results for branch branch-2.0
[build #922 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/922//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [amv2] Don't throw UnsupportedOperationException when rollback called on
> Assign/Unassign; spiral of death
> ---------------------------------------------------------------------------------------------------------
>
> Key: HBASE-21271
> URL: https://issues.apache.org/jira/browse/HBASE-21271
> Project: HBase
> Issue Type: Bug
> Components: amv2
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch
>
>
> I can't repro reliably but if an AssignProcedure or UnassignProcedure is a
> subprocedure of an Enable/Disable and for whatever reason the parent decides
> it needs to rollback -- can't get an entity lock -- it will ask the
> subprocedures to rollback. UP and AP don't support rollback on all steps. For
> steps where not supported, we have been throwing a
> UnsupportedOperationException.... The Framework reschedules the rollback. And
> so on filling logs and Procedure WALs.
> Instead just note no rollback supported and intervention may be needed (until
> we to to 2.2 when AP/UP go away).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
