You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Xudong Ni (JIRA)" <ji...@apache.org> on 2019/07/15 20:58:00 UTC
[jira] [Assigned] (MESOS-8636) Master should store `completed`
frameworks for lifecycle enforcement separately from that for webUI and
endpoints
[ https://issues.apache.org/jira/browse/MESOS-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xudong Ni reassigned MESOS-8636:
--------------------------------
Assignee: Xudong Ni
> 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
> Assignee: Xudong Ni
> 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.14#76016)