[
https://issues.apache.org/jira/browse/HADOOP-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673620#comment-16673620
]
Hadoop QA commented on HADOOP-15897:
------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} HADOOP-15897 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-15897 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12946726/HADOOP-15897.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15460/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Port range binding fails due to socket bind race condition
> ----------------------------------------------------------
>
> Key: HADOOP-15897
> URL: https://issues.apache.org/jira/browse/HADOOP-15897
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.0.2-alpha
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Major
> Attachments: HADOOP-15897.patch
>
>
> Java's {{ServerSocket#bind}} does both a bind and listen. At a system level,
> multiple processes may bind to the same port but only one may listen. Java
> sockets are left in an unrecoverable state when a process loses the race to
> listen first.
> Servers that compete over a listening port range (ex. App Master) will fail
> the entire range after a collision. The IPC layer should make a better
> effort to recover from failed binds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
