[
https://issues.apache.org/jira/browse/HBASE-21271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-21271:
--------------------------
Description:
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).
> [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
>
>
> 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)
