[ https://issues.apache.org/jira/browse/MESOS-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Wu reassigned MESOS-7947: -------------------------------- Assignee: Joseph Wu (was: Qian Zhang) I see three distinct, and possibly complimentary approaches to getting GC into nested containers: # We can add a new Agent API, like {{GC_NESTED_CONTAINER}}, which can be called after the launch of a nested container. This call would either mark the nested sandbox for GC like any other sandbox, or would manually schedule the GC for some time in the future. # We can extend the {{LAUNCH_NESTED_CONTAINER}} call with a field that tells the agent to schedule GC of the nested sandbox upon the nested container's exit. We might give this field a default value to retain the current leaky behavior, or opt to GC by default. # We can silently schedule nested sandboxes for GC. We might even do so based on the agent's {{gc_disk_headroom}} and {{gc_delay}} and the task's {{disk}} resource (which means instant GC for tasks that request 0 disk). [~qianzhang] I'm wondering if you have any thoughts about this (being the previous assignee). > Add GC capability to nested containers > -------------------------------------- > > Key: MESOS-7947 > URL: https://issues.apache.org/jira/browse/MESOS-7947 > Project: Mesos > Issue Type: Improvement > Components: executor > Reporter: Chun-Hung Hsiao > Assignee: Joseph Wu > Priority: Major > > We should extend the existing API or add a new API for nested containers for > an executor to tell the Mesos agent that a nested container is no longer > needed and can be scheduled for GC. > Related issue: MESOS-7939 -- This message was sent by Atlassian JIRA (v7.6.3#76005)