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

Yan Xu commented on MESOS-1719:
-------------------------------

[~adam-mesos] does this being labelled {{mesosphere}} mean this is on your 
roadmap in the near to medium term?

> Master should persist active frameworks information
> ---------------------------------------------------
>
>                 Key: MESOS-1719
>                 URL: https://issues.apache.org/jira/browse/MESOS-1719
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Vinod Kone
>            Assignee: Yongqiao Wang
>              Labels: mesosphere, reliability
>
> https://issues.apache.org/jira/browse/MESOS-1219 disallows completed 
> frameworks from re-registering with the same framework id, as long as the 
> master doesn't failover.
> This ticket tracks the work for it work across the master failover using 
> registrar.
> There are some open questions that need to be addressed:
> --> Should registry contain framework ids only framework infos.
>     For disallowing completed frameworks from re-registering, persisting     
>     framework ids is enough. But, if in the future, we want to disallow
>     frameworks from re-registering if some parts of framework info
>     changed then we need to persist the info too.
> --> How to update the framework info.
>       Currently frameworks are allowed to update framework info while re-
>       registering, but it only takes effect on the master when the master 
> fails 
>       over and on the slave when the slave fails over. How should things 
>        change when persist framework info?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to