[jira] [Updated] (YARN-7916) Remove call to docker logs on failure in container-executor
[
https://issues.apache.org/jira/browse/YARN-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated YARN-7916:
--
Labels: Docker (was: )
> 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
> Labels: Docker
> Fix For: 3.1.0
>
> 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
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7916) Remove call to docker logs on failure in container-executor
[
https://issues.apache.org/jira/browse/YARN-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Kumpf updated YARN-7916:
--
Attachment: YARN-7916.001.patch
> 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
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7916) Remove call to docker logs on failure in container-executor
[
https://issues.apache.org/jira/browse/YARN-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Kumpf updated YARN-7916:
--
Attachment: (was: YARN-7916.001.patch)
> 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
>
> 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
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7916) Remove call to docker logs on failure in container-executor
[
https://issues.apache.org/jira/browse/YARN-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Kumpf updated YARN-7916:
--
Attachment: YARN-7916.001.patch
> 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
(v7.6.3#76005)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
