[
https://issues.apache.org/jira/browse/MESOS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798060#comment-13798060
]
Ross Allen commented on MESOS-417:
----------------------------------
The source of this problem is master and slave allowing frameworks to register
with IDs already used by completed frameworks. The UI expects framework IDs to
be unique, and so when it finds a framework both in the active list and in the
completed list, it shows the data from the active framework and marks it as
completed.
The master and slave should not allow framework registration with an ID that
already appears in the completed frameworks list. That would prevent this issue
from happening in the web UI.
> Webui shows "This framework has terminated" after framework re-registration.
> ----------------------------------------------------------------------------
>
> Key: MESOS-417
> URL: https://issues.apache.org/jira/browse/MESOS-417
> Project: Mesos
> Issue Type: Bug
> Components: webui
> Reporter: Benjamin Mahler
>
> This is because the webui gets the state from the master, which includes a
> completed and active framework with the same FrameworkID. The webui URLs are
> not sufficient to disambiguate this case:
> http://<foo>.com:5050/#/frameworks/201103282247-0000000019-0000
> We should prioritize the active framework, and still allow for the completed
> framework to be viewed as well.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
