[
https://issues.apache.org/jira/browse/HADOOP-16312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850072#comment-16850072
]
Eric Yang commented on HADOOP-16312:
------------------------------------
{quote}Can you please explain it in more details? I think dumb-init executes
subprocesses in the foreground but I may be wrong.{quote}
This is different what I observed in the image before and I could be wrong
about dumb-init does a background push. Since it is running in the foreground,
we can discard this.
{quote}Are you sure? Do you have any method to prove it? According to my tests
dumb-init signals all the child processes in the hierarchy.{quote}
Sometimes docker kill -s SIGINT [container-id] did not work, but it is hard to
reproduce. Do we really need the bash between Java process and dumb-init? My
impression is no, and we can reclaim resource sooner.
> Remove dumb-init from hadoop-runner image
> -----------------------------------------
>
> Key: HADOOP-16312
> URL: https://issues.apache.org/jira/browse/HADOOP-16312
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Elek, Marton
> Priority: Major
>
> This issue is reported by [~eyang] in HDDS-1495.
> I think it's better to discuss under a separated issue as it's unrelated to
> HDDS-1495.
> The original problem description from [~eyang]
> {quote}Dumb-init is one way to always run contaized program in the
> background and respawn the program when program fails. This is poor man’s
> solution for keeping program alive.
> Cluster management software like Kubernetes or YARN have additional policy
> and logic to start the same docker container on a different node. Therefore,
> Dumb-init is not recommended for future Hadoop daemons instead allow cluster
> management software to make decision where to start the container. Dumb-init
> for demonize docker container will be removed, and change to use
> entrypoint.sh Docker provides -d flag to demonize foreground process. Most of
> the management system built on top of Docker, (ie. Kitematic, Apache YARN,
> and Kubernetes) integrates with Docker container at foreground to aggregate
> stdout and stderr output of the containerized program.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]