hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Badger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7916) Remove call to docker logs on failure in container-executor
Date Thu, 15 Feb 2018 22:59:02 GMT

    [ https://issues.apache.org/jira/browse/YARN-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366376#comment-16366376

Eric Badger commented on YARN-7916:

+1 (non-binding) looks good to me

> Remove call to docker logs on failure in container-executor
> -----------------------------------------------------------
>                 Key: YARN-7916
>                 URL: https://issues.apache.org/jira/browse/YARN-7916
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Shane Kumpf
>            Assignee: Shane Kumpf
>            Priority: Major
>         Attachments: YARN-7916.001.patch
> If a Docker container fails with a non-zero exit code, container-executor attempts to
run a {{docker logs --tail=250 container_name}} to provide more details on why the container
failed. While the idea is good, the current implementation will fail for most containers as
they are leveraging a launch script whose output will be redirected to a file. The {{--tail}} option
throws an error if no log output is available for the container, resulting in the docker logs
command returning rc=1 in most cases.
> I propose we remove this code from container-executor. Alternative approaches to handle
logging can be explored as part of supporting an image's entrypoint.

This message was sent by Atlassian JIRA

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

View raw message