You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bhuvan Arumugam (JIRA)" <ji...@apache.org> on 2014/09/17 01:22:33 UTC

[jira] [Updated] (MESOS-1219) Master should disallow frameworks that reconnect after failover timeout.

     [ https://issues.apache.org/jira/browse/MESOS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bhuvan Arumugam updated MESOS-1219:
-----------------------------------
    Fix Version/s:     (was: 0.21.0)
                   0.20.1

> Master should disallow frameworks that reconnect after failover timeout.
> ------------------------------------------------------------------------
>
>                 Key: MESOS-1219
>                 URL: https://issues.apache.org/jira/browse/MESOS-1219
>             Project: Mesos
>          Issue Type: Bug
>          Components: master, webui
>            Reporter: Robert Lacroix
>            Assignee: Vinod Kone
>             Fix For: 0.20.1
>
>
> When a scheduler reconnects after the failover timeout has exceeded, the framework id is usually reused because the scheduler doesn't know that the timeout exceeded and it is actually handled as a new framework.
> The /framework/:framework_id route of the Web UI doesn't handle those cases very well because its key is reused. It only shows the terminated one.
> Would it make sense to ignore the provided framework id when a scheduler reconnects to a terminated framework and generate a new id to make sure it's unique?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)