mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongqiao Wang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-1719) Master should persist active frameworks information
Date Thu, 21 Jan 2016 06:45:39 GMT

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

Yongqiao Wang edited comment on MESOS-1719 at 1/21/16 6:45 AM:
---------------------------------------------------------------

Patch for adding the protobufs in registry to persist some framework informations which do
not allow to change when framework re-register.
https://reviews.apache.org/r/42591/


was (Author: gradywang):
Patch for adding the protobufs in registry to persist some framework information which do
not allowed to changed when framework re-register.
https://reviews.apache.org/r/42591/

> 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)

Mime
View raw message