[jira] [Commented] (MESOS-1219) Master should generate new id for frameworks that reconnect after failover timeout

["Vinod Kone (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973599#comment-13973599 ] 

Vinod Kone commented on MESOS-1219:
-----------------------------------

There has been some conversations on our mailing list recently about this issue. The tl:dr; is that we need framework persistence in the master to be able to tackle this correctly.

> Master should generate new id for 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
>
> 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.2#6252)