[
https://issues.apache.org/jira/browse/MESOS-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148031#comment-15148031
]
Yongqiao Wang edited comment on MESOS-1719 at 2/16/16 2:48 AM:
---------------------------------------------------------------
Thank you [~neilc] and [~kaysoky], I find that *state* object is an internal
object of *RegistrarProcess*, if we want to use it directly in master.cpp to
persist framework info, then we need to expose it firstly. Another question is
why we should use *state abstraction* for framework info persistence? what is
the benefit for it? My original idea is to use *registry* directly (Like the
current implementation in above patches), then it can keep consistence with
slave info persistence in master component.
was (Author: gradywang):
Thank you [~neilc] and [~kaysoky], I find that `state` object is an internal
object of `RegistrarProcess`, if we want to use it directly in master.cpp to
persist framework info, then we need to expose it firstly. Another question is
why we should use 'state abstraction' for framework info persistence? what is
the benefit for it? My original idea is to use `registry` directly (Like the
current implementation in above patches), then it can keep consistence with
slave info persistence in master component.
> 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
>
> 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)
