[
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-21271:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 2.2.0)
Status: Resolved (was: Patch Available)
Pushed to branch-2.0 and branch-2.1. Doesn't make sense on branch-2+.
I see it makes a difference in testing in that the failed rollback eventually
finishes where previous it would just cycle forever.
> [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.1.1, 2.0.3
>
> Attachments: HBASE-21271.branch-2.1.001.patch,
> HBASE-21271.branch-2.1.002.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)
