You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "yuhuiyang (JIRA)" <ji...@apache.org> on 2019/06/27 03:13:00 UTC
[jira] [Comment Edited] (HBASE-22631) assign failed may make gced
parent region appear again !!!
[ https://issues.apache.org/jira/browse/HBASE-22631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873779#comment-16873779 ]
yuhuiyang edited comment on HBASE-22631 at 6/27/19 3:12 AM:
------------------------------------------------------------
I will submit a correct named patch later !
was (Author: yu-huiyang):
i will submit a correct named patch later !
> assign failed may make gced parent region appear again !!!
> ----------------------------------------------------------
>
> Key: HBASE-22631
> URL: https://issues.apache.org/jira/browse/HBASE-22631
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Affects Versions: 2.1.1
> Reporter: yuhuiyang
> Priority: Major
>
> When i assign a region A the process is as follows:
> step1 : A is assigned to rs1 , and rs1 fails to open it .
> step2 : assignProcedure handleFailure .
> step3 : A is assign to rs2 and rs success to open it .
> Above is the normal flow . However when rs1 is restart after the reigon A was split and GCRegionProcedure was successed , the region A appare again !
> The region is that reigon A is not removed from the serverMap correctly when assignprocedure handleFailure . Because the code regionNode.offline() make the regionNode's regionLocation to be null and make regionNode's state to OFFLINE . So when the code env.getAssignmentManager().undoRegionAsOpening(regionNode) do nothing . So when the rs1 restart event triggers a serverCrashProcedure, it will get reigons from serverMap and it will get the region A then A will be assigned and hdfs dir will be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)