[
https://issues.apache.org/jira/browse/HBASE-18984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205208#comment-16205208
]
Yi Liang commented on HBASE-18984:
----------------------------------
The reason why retain assignment does not work well after disable/enable is
that every time we unsign the region, we mark the regionLocation as null in
regionStateNode, and when we assign the region, it will load the this null as
current region location, and if the region location is null, AM will assign it
a random region server to it.
Have already fixed above issues, but see other errors when restart cluster.
Still debugging.
> [AMv2] Retain assignment does not work well in AMv2
> ---------------------------------------------------
>
> Key: HBASE-18984
> URL: https://issues.apache.org/jira/browse/HBASE-18984
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Affects Versions: 2.0.0
> Reporter: Yi Liang
> Assignee: Yi Liang
> Fix For: 2.0.0
>
> Attachments: Screen Shot 2017-10-10 at 2.24.19 PM.png
>
>
> work on 8.17 Retain assignment in
> https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.epjn9nege80k
> To reproduce this error, in hbase shell:
> createTable t1 --> list_regions 't1' --> disable 't1' ---> enable 't1' -->
> list_reigons 't1' (maybe you need to try enable/disable multiple times)
> See attached images. same region assigned to different region servers
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
