[
https://issues.apache.org/jira/browse/HBASE-21934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782029#comment-16782029
]
Hudson commented on HBASE-21934:
--------------------------------
Results for branch branch-2.2
[build #74 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/74/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/74//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/74//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/74//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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.branch-2.001.patch,
> HBASE-21934.branch-2.1.001.patch, HBASE-21934.branch-2.1.001.patch,
> HBASE-21934.branch-2.2.001.patch, 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)
