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 "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 12:35:00 UTC
[jira] [Commented] (HADOOP-15897) Port range binding fails due to socket bind race condition
[ https://issues.apache.org/jira/browse/HADOOP-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803131#comment-17803131 ]
Shilun Fan commented on HADOOP-15897:
-------------------------------------
Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a blocker. Retarget 3.5.0.
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org