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

Nicolas Liochon commented on HBASE-10573:
-----------------------------------------

in 0.98 and previous, it's the only solution to limit the impact of 
hbase.rpc.timeout. In trunk we're a little bit better since I decoupled the 
socket timeout from the rpc timeout, but it's still fresh, and as well 
multicasting the message will still be more efficient, by ~10 seconds in many 
cases. So yes, I really want to keep it.

I can give a try to the Netty 4 conversion, but not before end of next week, or 
may be in two weeks.

> Use Netty 4
> -----------
>
>                 Key: HBASE-10573
>                 URL: https://issues.apache.org/jira/browse/HBASE-10573
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: hbase-10191
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>         Attachments: 10573.patch, 10573.patch
>
>
> Pull in Netty 4 and sort out the consequences.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to