Robert Lacroix created MESOS-1219:
-------------------------------------
Summary: 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)
