You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Xiao Chen (JIRA)" <ji...@apache.org> on 2015/12/01 00:09:11 UTC
[jira] [Commented] (HADOOP-12605) Fix intermittent failure of
TestIPC.testIpcWithReaderQueuing
[ https://issues.apache.org/jira/browse/HADOOP-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032688#comment-15032688 ]
Xiao Chen commented on HADOOP-12605:
------------------------------------
Hi [~iwasakims],
Thanks for looking into this issue! It's great that you looked into the implementation of the {{Server}} class. :) - I stopped after looking HADOOP-9956 when I tried to fix HADOOP-10406 and thought it's just a test failure. Thanks for inspiring me to look into the implementation, and good RCA overall.
Your 1st comment (the {{maxAccept > server.getNumOpenConnections()}} case) makes sense to me.
The 2nd comment (the {{maxAccept < server.getNumOpenConnections()}} case), I could be wrong, but in test we block all the calls so this shouldn't happen in the test case, right?
The 3rd comment (the {{maxAccept < server.getNumOpenConnections()}} in {{checkBlocking(1, 1, 1)}} case), since in {{Connection#readAndProcess}} we have the following code, so even for new client connections 1 rpc call should be processed too. I confirmed this by some console printing.
{code} boolean isHeaderRead = connectionContextRead; {code}
I guess you're probably already working on it - I think it'd be great if we can manage to 100% reproduce the issue first.
> Fix intermittent failure of TestIPC.testIpcWithReaderQueuing
> ------------------------------------------------------------
>
> Key: HADOOP-12605
> URL: https://issues.apache.org/jira/browse/HADOOP-12605
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Priority: Minor
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)