[
https://issues.apache.org/jira/browse/HBASE-13823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-13823:
---------------------------------------
Resolution: Fixed
Hadoop Flags: Incompatible change
Fix Version/s: 2.0.0
Release Note:
For cluster upgraded from 1.0.x or older releases, master startup would not
continue the in-progress enable/disable table process. If orphaned znode with
ENABLING/DISABLING state exists in the cluster, run hbck or manually fix the
issue.
For new cluster or cluster upgraded from 1.1.x and newer release, there is no
issue to worry about.
Status: Resolved (was: Patch Available)
> 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
> Fix For: 2.0.0
>
> Attachments: HBASE-13823-v0.patch, HBASE-13823-v1.patch,
> HBASE-13823-v2.patch, HBASE-13823-v3.patch, HBASE-13823-v4.patch,
> HBASE-13823.v5-master.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)
