[
https://issues.apache.org/jira/browse/YARN-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100062#comment-16100062
]
Shane Kumpf commented on YARN-6726:
-----------------------------------
Thanks for the review, [~wangda].
I will add additional validation of the container name.
Regarding #2, let me try to explain with an example.
We run {{docker inspect}} via
{{PrivilegedOperationExecutor#executePrivilegedOperation}} and one of the
options is to "grabOutput" from the command executed by c-e. In the {{docker
inspect}} case, this is the IP address and hostname of the container. LOGFILE
is set to stdout, which is where {{docker inspect}} output is "grabbed" from.
When the fflush occurs on the LOGFILE, "grabOutput" returns not only the output
from {{docker inspect}} but also this log entry. Note in the output below how
the "IP" entry for the container is the log entry and not the IP address. Let
me know if this is still unclear.
{code}
2017-07-25 13:30:03,596 DEBUG
org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Sending out 1
container statuses: [ContainerStatus: [ContainerId:
container_1500987852094_0001_01_000001, ExecutionType: GUARANTEED, State:
RUNNING, Capability: <memory:2048, vCores:1>, Diagnostics: , ExitStatus: -1000,
IP: [ Using command inspect
--format='{{range(.NetworkSettings.Networks)}}{{.IPAddress}},
{{end}}{{.Config.Hostname}}' container_1500987852094_0001_01_000001], Host:
localhost.localdomain]]
{code}
> Fix issues with docker commands executed by container-executor
> --------------------------------------------------------------
>
> Key: YARN-6726
> URL: https://issues.apache.org/jira/browse/YARN-6726
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Shane Kumpf
> Assignee: Shane Kumpf
> Attachments: YARN-6726.001.patch
>
>
> docker inspect, rm, stop, etc are issued through container-executor. Commands
> other than docker run are not functioning properly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
