[
https://issues.apache.org/jira/browse/HBASE-24885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178794#comment-17178794
]
Pankaj Kumar commented on HBASE-24885:
--------------------------------------
Thanks for finding this issue [~Bo Cui].
When we assign explicitly a region which is in already OPEN state then it may
lead to Double Assignment or stuck in RIT.
If HMaster choose the same server for assignment where it is already OPEN then
RS will reject the request saying already OPEN and region will stuck in RIT,
otherwise double assignment problem will happen.
We need add prevalidation logic before creating TRSP for this case. Ping
[~stack] [~zhangduo].
> STUCK RIT by hbck2 assigns
> --------------------------
>
> Key: HBASE-24885
> URL: https://issues.apache.org/jira/browse/HBASE-24885
> Project: HBase
> Issue Type: Bug
> Components: hbck2, Region Assignment
> Affects Versions: 3.0.0-alpha-1, 2.2.3
> Reporter: Bo Cui
> Priority: Major
>
> If a region has been assign to rs1 and then client assigns region again by
> "hbck2 assigns"
> 1、if regionPlan is region to be assign to rs2，the region will be opened on
> rs1 and rs2.
> master log:
> {quote}WARN org.apache.hadoop.hbase.master.assignment.AssignmentManager:
> rit=OPEN, location=rs2, table=tableName, region=reionName reported OPEN on
> server=rs1 but state has otherwise
> {quote}
> 2、if regionPlan is region to be assign to rs1， the
> TransitRegionStateProcedure and OpenRegionProcedure will stuck. because rs1
> is not responding to master
> rslog:
> {quote}Receiving OPEN for the region:{}, which we are already trying to OPEN
> - ignoring this new request for this region.
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
