[
https://issues.apache.org/jira/browse/MESOS-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542684#comment-16542684
]
Qian Zhang commented on MESOS-7947:
-----------------------------------
For 2, It seems agent will not be notified with the nested container's exit, or
we want agent to schedule the GC for the nested container when it receives the
terminal state update of the corresponding task?
For 3, I am not sure how to do it silently, the handler of the API
{{LAUNCH_NESTED_CONTAINER}} calls {{containerizer->launch()}} directly, so
agent itself is even not aware of launching nested container.
I'd prefer solution 1, but the problem is, what is the timing for the executor
to call {{GC_NESTED_CONTAINER}}? Once the executor is notified by agent that
the nested container terminates? And instead of introducing a new agent API to
GC nested container, can we just let the executor to call the existing agent
API {{REMOVE_CONTAINER}}? And we may need to add an optional field in
{{TaskInfo}} (something like {{GCPolicy}}) so that the executor know when to GC
the nested container, if this field is not specified, we just retain the
current behavior for backward compatibility. But that seems not a general field
(more like a nested container specific field) which is unfortunate.
> 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)
