You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nihal Jain (JIRA)" <ji...@apache.org> on 2019/01/28 08:38:00 UTC

[jira] [Updated] (HBASE-21795) Client application may get stuck (time bound) if a table modify op is called immediately after split op

     [ https://issues.apache.org/jira/browse/HBASE-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nihal Jain updated HBASE-21795:
-------------------------------
    Attachment: HBASE-21795.master.001.patch

> 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)