[
https://issues.apache.org/jira/browse/MESOS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone resolved MESOS-1219.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.21.0
commit e9643f47720d8c5c9e6278ec068e771b94e94fbc
Author: Vinod Kone <[email protected]>
Date: Fri Apr 18 15:31:59 2014 -0700
Fixed master to reject completed frameworks from re-registering.
Review: https://reviews.apache.org/r/20507
> 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.21.0
>
>
> 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)
