[
https://issues.apache.org/jira/browse/HBASE-13823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598132#comment-14598132
]
Ted Yu commented on HBASE-13823:
--------------------------------
{code}
1721 LOG.warn("Unable to find a pending EnableTableProcedure for
table " + tableName +
1722 ". running starting a new Enable operation.");
1723
ProcedureSyncWait.submitAndWaitProcedure(server.getMasterProcedureExecutor(),
1724 new
DisableTableProcedure(server.getMasterProcedureExecutor().getEnvironment(),
{code}
LOG says EnableTableProcedure but the actual procedure is DisableTableProcedure
> Procedure V2: unnecessaery operaions on
> AssignmentManager#recoverTableInDisablingState() and
> recoverTableInEnablingState()
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-13823
> URL: https://issues.apache.org/jira/browse/HBASE-13823
> Project: HBase
> Issue Type: Sub-task
> Components: master, proc-v2
> Affects Versions: 2.0.0, 1.2.0
> Reporter: Stephen Yuan Jiang
> Assignee: Stephen Yuan Jiang
> Attachments: HBASE-13823-v0.patch, HBASE-13823-v1.patch
>
>
> AssignmentManager#recoverTableInDisablingState() and
> AssignmentManager#recoverTableInEnablingState try to complete unfinished
> enable/disable table operations. In the past, it is necessary, as master
> failure could leave table in bad state. With HBASE-13211, enable/disable
> operations would be auto-recover by Procedure-V2 logic. Those recovery
> operation is not necessary: we can either remove those recovery operation or
> not replay enable/disable operations in procedure queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
