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

Hudson commented on HBASE-16654:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #1648 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1648/])
HBASE-16654 Better handle channelInactive and close for netty rpc client 
(zhangduo: rev 5568929dd2bfc20c1aa15d37d318459888cbd32a)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/NettyRpcDuplexHandler.java
* (delete) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/AsyncHBaseSaslRpcClientHandler.java
* (delete) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/AsyncHBaseSaslRpcClient.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/BufferCallBeforeInitHandler.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslWrapHandler.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/NettyRpcConnection.java
* (add) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/NettyHBaseSaslRpcClientHandler.java
* (add) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/NettyHBaseSaslRpcClient.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/SaslUnwrapHandler.java


> Better handle channelInactive and close for netty rpc client
> ------------------------------------------------------------
>
>                 Key: HBASE-16654
>                 URL: https://issues.apache.org/jira/browse/HBASE-16654
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16654.patch
>
>
> We should pass the event to the next handler in the pipeline as 
> channelInactive and close are usually used as the cleanup method of a 
> ChannelHandler.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to