[
https://issues.apache.org/jira/browse/HBASE-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753804#comment-16753804
]
Nihal Jain commented on HBASE-21795:
------------------------------------
{quote}So the ModifyTableProcedure completes successfully, but the client does
not know it?
{quote}
Yes because the way out modify table future checks for table modification, it
expects all regions are in opened state for the table, but there will be parent
region in split state. Submitted a patch which reproduces the bug and proposes
a fix. Merge does not have this problem.
> 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)
