[
https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130584#comment-15130584
]
Joseph Wu commented on MESOS-1719:
----------------------------------
Would it be possible to utilize the "state abstraction" instead? For example,
Marathon keeps its persistent state via these classes:
https://github.com/apache/mesos/blob/master/src/state/state.hpp
https://github.com/apache/mesos/blob/master/src/java/src/org/apache/mesos/state/State.java
https://github.com/mesosphere/marathon/blob/master/src/main/scala/mesosphere/util/state/mesos/MesosStateStore.scala
> Master should persist active frameworks information
> ---------------------------------------------------
>
> Key: MESOS-1719
> URL: https://issues.apache.org/jira/browse/MESOS-1719
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
> Assignee: Yongqiao Wang
>
> 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.3.4#6332)
