[
https://issues.apache.org/jira/browse/HBASE-20976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569191#comment-16569191
]
stack commented on HBASE-20976:
-------------------------------
[~allan163] I backported HBASE-20708 yesterday. Should we close this now?
I've been backporting the main AMv2 changes up in branch-2.1 to branch-2.0 over
the last few days after first trying patches on cluster.... Patches are big but
I see them as bug-fixes, critical ones.. AMv2 has to work well when folks go to
use hbase2, even for those who try hbase-2.0.x first. It is taking a while as I
test before commit. I'm almost caught up.
> SCP can be scheduled multiple times for the same RS
> ---------------------------------------------------
>
> Key: HBASE-20976
> URL: https://issues.apache.org/jira/browse/HBASE-20976
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.1
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
> Fix For: 2.0.2
>
> Attachments: HBASE-20976.branch-2.0.001.patch
>
>
> SCP can be scheduled multiple times for the same RS:
> 1. a RS crashed, a SCP was submitted for it
> 2. before this SCP finish, the Master crashed
> 3. The new master will scan the meta table and find some region is still open
> on a dead server
> 4. The new master submit a SCP for the dead server again
> The two SCP for the same RS can even execute concurrently if without
> HBASE-20846…
> Provided a test case to reproduce this issue and a fix solution in the patch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
