hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18199) Race in NettyRpcConnection may cause call stuck in BufferCallBeforeInitHandler forever
Date Sat, 10 Jun 2017 13:43:19 GMT

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

Hudson commented on HBASE-18199:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-2.0 #21 (See [https://builds.apache.org/job/HBase-2.0/21/])
HBASE-18199 Race in NettyRpcConnection may cause call stuck in (zhangduo: rev eca1ec335667429896c40106e584128bdc5f90b8)
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/NettyRpcConnection.java


> Race in NettyRpcConnection may cause call stuck in BufferCallBeforeInitHandler forever
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-18199
>                 URL: https://issues.apache.org/jira/browse/HBASE-18199
>             Project: HBase
>          Issue Type: Bug
>          Components: IPC/RPC
>    Affects Versions: 3.0.0, 1.4.0, 2.0.0-alpha-1
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 3.0.0, 1.4.0, 2.0.0-alpha-2
>
>         Attachments: HBASE-18199.patch, HBASE-18199-v1.patch
>
>
> Found this when implementing the POC of HDFS-9924.
> The problem is that channel.writeAndFlush will find the first outbound handler before
scheduling the actual write task into event loop, so it is possible that when we actually
execute the write task, the first outbound handler has already been changed but the task still
refers to the old handler which has already been removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message