hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-16312) Remove dumb-init from hadoop-runner image
Date Mon, 13 May 2019 10:52:00 GMT
Elek, Marton created HADOOP-16312:

             Summary: 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

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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message