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

Yan Xu commented on MESOS-8636:
-------------------------------

This is in line with what Mesos already does for [gone 
agents|https://github.com/apache/mesos/blob/76c38f9d03ee6854e6bcd00a959d697472e0ea58/src/master/registry.proto#L62]
 and should still be valid when we introduce framework persistence MESOS-1719 
because we'll likely store only the framework IDs in the registry and 
reconstruct the full framework archive data from agents. 

> Master should store `completed` frameworks for lifecycle enforcement 
> separately from that for webUI and endpoints
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-8636
>                 URL: https://issues.apache.org/jira/browse/MESOS-8636
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Yan Xu
>            Priority: Major
>
> Currently the master stores the history of completed frameworks in a map with 
> the full historical data of the framework.
> {code:title=}
> struct Frameworks 
> {
>   BoundedHashMap<FrameworkID, process::Owned<Framework>> completed;
> }
> {code}
> This map serves the purposes of
> # Rejecting frameworks from reregistering if they have previously marked as 
> completed.
> # Displaying the history of this framework (i.e., its tasks) via webUI and 
> endpoints.
> However because the full framework object is large, it could be prohibitively 
> expensive to keep a long history for its relatively low importance.
> However for 1, we only need to persist the framework ID and keeping a longer 
> history is essential to the integrity of the cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to