You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2017/02/07 18:31:41 UTC
[jira] [Updated] (MESOS-6033) Scheduler library's reconnection
logic should be teardown-aware
[ https://issues.apache.org/jira/browse/MESOS-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anand Mazumdar updated MESOS-6033:
----------------------------------
Labels: mesosphere newbie (was: mesosphere)
> Scheduler library's reconnection logic should be teardown-aware
> ---------------------------------------------------------------
>
> Key: MESOS-6033
> URL: https://issues.apache.org/jira/browse/MESOS-6033
> Project: Mesos
> Issue Type: Improvement
> Components: HTTP API
> Affects Versions: 1.0.0, 1.0.1
> Reporter: Greg Mann
> Labels: mesosphere, newbie
>
> The reconnection logic in the scheduler library currently is not aware of any explicit teardown calls sent by the scheduler to the master. This means that after a scheduler has explicitly torn itself down, it will attempt a reconnection to master under the covers, and if this succeeds the scheduler's {{connected}} callback will be invoked. This forces frameworks to implement their own teardown awareness logic in their callbacks.
> We should add teardown-awareness to the scheduler library's reconnection code so that framework authors don't have to worry about this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)