Yan Xu created MESOS-1560:
-----------------------------
Summary: Libprocess SocketManager drains ephemeral ports when
trying to connect to a dead remote socket
Key: MESOS-1560
URL: https://issues.apache.org/jira/browse/MESOS-1560
Project: Mesos
Issue Type: Bug
Reporter: Yan Xu
Priority: Minor
Currently SocketManager allocates a new ephemeral port when it tries to
communicate with a remote socket if one active socket is not created and kept
alive for that remote socket.
When the remote socket closes (e.g. Scheduler tries to talk to master and
master terminates), SocketManager closes the local socket. However since the
local port stays in TIME_WAIT state for a while, in extreme cases where the
local SocketManager keeps retrying to connect to that dead remote socket *too
fast*, it can cause the local machine to run out of available ephemeral ports.
Can these ports in TIME_WAIT be *reused* by SocketManager to avoid the problem?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
