hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8097) TestRPCCallBenchmark failing w/ port in use -handling badly
Date Tue, 21 Feb 2012 12:58:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212562#comment-13212562

Steve Loughran commented on HADOOP-8097:

running the test explicitly (rather than in the bulk test run) passes; a netstat run immediately
after shows 50+ TCP connections to port 12345 in TIME_WAIT, which is probably triggering the
timeout, as Both test cases in TestRPCCompatibility use the same (default) port of 12345.

I propose using an explicit port number in both as another argument. This will avoid inter-test
port clashes, in which test #2 runs while the socket is still in TIME_WAIT.

Sans doesn't note anything legitmate running on this port number, but as most traffic is trojan
it is probably best to change to a new value

ports [12350, 12351] appear low risk
> TestRPCCallBenchmark failing w/ port in use -handling badly
> -----------------------------------------------------------
>                 Key: HADOOP-8097
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8097
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.24.0
>            Reporter: Steve Loughran
>            Priority: Minor
> I'm seeing TestRPCCallBenchmark fail with port in use, which is probably related to some
other test (race condition on shutdown?), but which isn't being handled that well in the test
itself -although the log shows the binding exception, the test is failing on a connection

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


View raw message