[
https://issues.apache.org/jira/browse/HBASE-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756132#comment-16756132
]
Nihal Jain commented on HBASE-21795:
------------------------------------
{quote} clear parent region state from AssignmentMaanger's regionStates memory
(Similar as Merge region procedure flow)..
{quote}
We may clear parent region from AM in method
{{AssignmentManager.markRegionAsSplit()}} (similar to
{{MergeTableRegionsProcedure}}) but then we will need to handle and make sure
it does not break anything in the code. The {{RegionInfo.isSplit()}} check is
spread all across HBase code, which may become faulty if we delete split region
inside AssignmentManager.markRegionAsSplit(), and not wait for
{{CatalogJanitor}} to delete it after deleting HFiles.
I've discussed with [~Bhupendra] offline, he too agrees with this.
[^HBASE-21795.master.001.patch] looks fine, considering we shall not ever have
a split region in RIT (AFAIK AMv2 does not allow assigning a split region)
WDYT [~Apache9]?
> Client application may get stuck (time bound) if a table modify op is called
> immediately after split op
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-21795
> URL: https://issues.apache.org/jira/browse/HBASE-21795
> Project: HBase
> Issue Type: Bug
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Critical
> Attachments: HBASE-21795.master.001.patch
>
>
> *Steps:*
> * Create a table
> * Split the table
> * Modify the table immediately after splitting
> *Expected*:
> The modify table procedure completes and control returns back to client
> *Actual:*
> The modify table procedure completes and control does not return back to
> client, until catalog janitor runs and deletes parent or future timeout occurs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
