[
https://issues.apache.org/jira/browse/YARN-8777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622850#comment-16622850
]
Eric Yang commented on YARN-8777:
---------------------------------
[~ebadger] I am confused by your statement. We have been using comma delimited
launch command in .cmd file for ENTRYPOINT in Hadoop 3.1.1. YARN-8805 seems to
be a request to make sure the user supplied command with space delimited to be
converted to the common delimited format for exec. The requested change is on
Java side serialization. There is no changes in C code or .cmd format to
prevent breaking backward compatibility, if I understand the problem correctly.
The format was what we agreed upon without rewrite .cmd serialization
technique. What is the concern with launch_command deserialization delimited
by comma on C side? Should I change launch_command to a single parameter like
I suggested as a single binary to prevent inconsistent length of argv between
container-executor and docker exec?
> Container Executor C binary change to execute interactive docker command
> ------------------------------------------------------------------------
>
> Key: YARN-8777
> URL: https://issues.apache.org/jira/browse/YARN-8777
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zian Chen
> Assignee: Eric Yang
> Priority: Major
> Labels: Docker
> Attachments: YARN-8777.001.patch, YARN-8777.002.patch,
> YARN-8777.003.patch
>
>
> Since Container Executor provides Container execution using the native
> container-executor binary, we also need to make changes to accept new
> “dockerExec” method to invoke the corresponding native function to execute
> docker exec command to the running container.
--
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
