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

Posted to issues@hbase.apache.org by "Jingyun Tian (JIRA)" <ji...@apache.org> on 2019/02/25 09:38:00 UTC

[jira] [Updated] (HBASE-21934) RemoteProcedureDispatcher should track the ongoing dispatched calls

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

Jingyun Tian updated HBASE-21934:
---------------------------------
    Summary: RemoteProcedureDispatcher should track the ongoing dispatched calls  (was: SplitWALProcedure get stuck during ITBLL)

> RemoteProcedureDispatcher should track the ongoing dispatched calls
> -------------------------------------------------------------------
>
>                 Key: HBASE-21934
>                 URL: https://issues.apache.org/jira/browse/HBASE-21934
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.x
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>            Priority: Major
>             Fix For: 3.
>
>         Attachments: HBASE-21934.master.001.patch, HBASE-21934.master.002.patch
>
>
> I encounter the problem that when master assign a splitWALRemoteProcedure to a region server. The log of this region server says it failed to recover the lease of this file. Then this region server is killed by chaosMonkey. As the result, this procedure is not timeout and hang there forever.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)