[
https://issues.apache.org/jira/browse/HBASE-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432249#comment-13432249
]
Zhihong Ted Yu edited comment on HBASE-6414 at 8/9/12 10:40 PM:
----------------------------------------------------------------
Using the previous patch, I ran TestHMasterRPCException#testRPCException 3
times.
I saw the following twice:
{code}
Failed tests:
testRPCException(org.apache.hadoop.hbase.master.TestHMasterRPCException): Call
to lm-sjn-0071.y.com/10.246.12.139:55121 failed on socket timeout exception:
java.net.SocketTimeoutException: 100 millis timeout while waiting for channel
to be ready for read. ch : java.nio.channels.SocketChannel[connected ...
{code}
Can we not introduce loop but instead rely on some additional sleep ?
Thanks
was (Author: zhi...@ebaysf.com):
Using the previous patch, I ran TestHMasterRPCException#testRPCException 3
times.
I saw the following twice:
{code}
Failed tests:
testRPCException(org.apache.hadoop.hbase.master.TestHMasterRPCException): Call
to lm-sjn-00713032.corp.ebay.com/10.246.12.139:55121 failed on socket timeout
exception: java.net.SocketTimeoutException: 100 millis timeout while waiting
for channel to be ready for read. ch :
java.nio.channels.SocketChannel[connected ...
{code}
Can we not introduce loop but instead rely on some additional sleep ?
Thanks
> Remove the WritableRpcEngine & associated Invocation classes
> ------------------------------------------------------------
>
> Key: HBASE-6414
> URL: https://issues.apache.org/jira/browse/HBASE-6414
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.96.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.96.0
>
> Attachments: 6414-1.patch.txt, 6414-3.patch.txt, 6414-4.patch.txt,
> 6414-4.patch.txt, 6414-initial.patch.txt, 6414-initial.patch.txt
>
>
> Remove the WritableRpcEngine & Invocation classes once HBASE-5705 gets
> committed and all the protocols are rebased to use PB.
> Raising this jira in advance..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
