[
https://issues.apache.org/jira/browse/HADOOP-8097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212751#comment-13212751
]
Todd Lipcon commented on HADOOP-8097:
-------------------------------------
I'm not sure this is the best fix (relying on a different static port). A few
other ideas:
- change the benchmark so that if a port isn't specified, it binds to port 0,
and then has the clients connect to whichever port gets bound
- make sure it uses REUSEADDR so that it can still bind despite the TIME_WAIT
sockets
Either of those make sense? I honestly thought I'd written it to use port 0 but
apparently I didn't :)
> 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
> Components: ipc
> Affects Versions: 0.24.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.24.0
>
> Attachments: HADOOP-8097.patch
>
>
> 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 timeout
--
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
