[
https://issues.apache.org/jira/browse/MESOS-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339608#comment-15339608
]
Anand Mazumdar commented on MESOS-5359:
---------------------------------------
{noformat}
commit 948fe8c7b5b20dda5abd56ad64f4e5b28b8dc750
Author: Jose Guilherme Vanz <[email protected]>
Date: Mon Jun 20 07:15:02 2016 -0700
Delay before initiating a connection with master.
The scheduler library has been updated to wait before initiating a
connection with the master. The maximum amount of time waited by
the library is defined by the flag: `connection_delay_max`. For
tests, we default the delay to 0 to speed up the tests.
Review: https://reviews.apache.org/r/48387/
{noformat}
> The scheduler library should have a delay before initiating a connection with
> master.
> -------------------------------------------------------------------------------------
>
> Key: MESOS-5359
> URL: https://issues.apache.org/jira/browse/MESOS-5359
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Anand Mazumdar
> Assignee: José Guilherme Vanz
> Labels: mesosphere
> Fix For: 1.0.0
>
>
> Currently, the scheduler library {{src/scheduler/scheduler.cpp}} does have an
> artificially induced delay when trying to initially establish a connection
> with the master. In the event of a master failover or ZK disconnect, a large
> number of frameworks can get disconnected and then thereby overwhelm the
> master with TCP SYN requests.
> On a large cluster with many agents, the master is already overwhelmed with
> handling connection requests from the agents. This compounds the issue
> further on the master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
