[
https://issues.apache.org/jira/browse/MESOS-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295246#comment-15295246
]
Anand Mazumdar commented on MESOS-5359:
---------------------------------------
[~jvanz] Thanks for taking this on.
The scope of the JIRA is to make the changes for the new API i.e. the scheduler
library here: {{src/scheduler/scheduler.cpp}} and not to the old driver based
interface {{src/sched/sched.cpp}}. A possible solution can be to introduce a
{{delay}} here:
https://github.com/apache/mesos/blob/master/src/scheduler/scheduler.cpp#L473
For more information about the new API see:
http://mesos.apache.org/documentation/latest/scheduler-http-api/
> 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: 0.29.0
> Reporter: Anand Mazumdar
> Assignee: José Guilherme Vanz
> Labels: mesosphere
>
> 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)
