You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2019/03/01 02:39:00 UTC

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

    [ https://issues.apache.org/jira/browse/HBASE-21934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781219#comment-16781219 ] 

Duo Zhang commented on HBASE-21934:
-----------------------------------

+1. Thanks for the patience. Please commit it to branch-2.1+ and I will start to roll the 2.1.4 release.

Thanks.

> 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
>          Components: proc-v2
>    Affects Versions: 2.x
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>            Priority: Blocker
>             Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.4
>
>         Attachments: HBASE-21934.master.001.patch, HBASE-21934.master.002.patch, HBASE-21934.master.003.patch, HBASE-21934.master.004.patch, HBASE-21934.master.005.patch, HBASE-21934.master.006.patch, HBASE-21934.master.007.patch, HBASE-21934.master.008.patch, HBASE-21934.master.009.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)