[
https://issues.apache.org/jira/browse/MESOS-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551342#comment-16551342
]
Vinod Kone edited comment on MESOS-7947 at 7/20/18 10:17 PM:
-------------------------------------------------------------
I like option 2) with the addition that we still leverage `gc_disk_headroom`
and `gc_delay`. -A downside of 1) is that every executor needs to implement its
own GC algorithm to figure out when to call REMOVE-. With 2) all those
executors that use LAUNCH_NESTED_CONTAINER can just set a boolean field
indicating that they want the container's sandbox to be GC'ed.
One limitation of 2) is that it only applies to executors that leverage LNC to
launch tasks. For multi-task executors that don't use that (e.g., long lived
executor in our tests), it doesn't apply.
was (Author: vinodkone):
I like option 2) with the addition that we still leverage `gc_disk_headroom`
and `gc_delay`. A downside of 1) is that every executor needs to implement its
own GC algorithm to figure out when to call REMOVE. With 2) all those executors
that use LAUNCH_NESTED_CONTAINER can just set a boolean field indicating that
they want the container's sandbox to be GC'ed.
One limitation of 2) is that it only applies to executors that leverage LNC to
launch tasks. For multi-task executors that don't use that (e.g., long lived
executor in our tests), it doesn't apply.
> 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)
