[
https://issues.apache.org/jira/browse/YARN-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621463#comment-14621463
]
Hadoop QA commented on YARN-3853:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 18m 7s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:green}+1{color} | tests included | 0m 0s | The patch appears to
include 3 new or modified test files. |
| {color:green}+1{color} | javac | 7m 52s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 48s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 22s | The applied patch does
not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle | 0m 49s | The applied patch generated
51 new checkstyle issues (total was 271, now 312). |
| {color:green}+1{color} | whitespace | 0m 36s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 20s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 1m 16s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:red}-1{color} | yarn tests | 6m 7s | Tests failed in
hadoop-yarn-server-nodemanager. |
| | | 46m 55s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests |
hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService
|
| | hadoop.yarn.server.nodemanager.containermanager.container.TestContainer |
| |
hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestLogAggregationService
|
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12744583/YARN-3853.001.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f4ca530 |
| checkstyle |
https://builds.apache.org/job/PreCommit-YARN-Build/8486/artifact/patchprocess/diffcheckstylehadoop-yarn-server-nodemanager.txt
|
| hadoop-yarn-server-nodemanager test log |
https://builds.apache.org/job/PreCommit-YARN-Build/8486/artifact/patchprocess/testrun_hadoop-yarn-server-nodemanager.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/8486/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf908.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/8486/console |
This message was automatically generated.
> Add docker container runtime support to LinuxContainterExecutor
> ---------------------------------------------------------------
>
> Key: YARN-3853
> URL: https://issues.apache.org/jira/browse/YARN-3853
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Sidharta Seethana
> Assignee: Sidharta Seethana
> Attachments: YARN-3853.001.patch
>
>
> Create a new DockerContainerRuntime that implements support for docker
> containers via container-executor. LinuxContainerExecutor should default to
> current behavior when launching containers but switch to docker when
> requested.
> Overview
> ===
> The current mechanism of launching/signaling containers is moved to its own
> (default) container runtime. In order to use docker container runtime a
> couple of environment variables have to be set. This will have to be
> revisited when we have a first class client side API to specify different
> container types and associated parameters. Using ‘pi’ as an example and using
> a custom docker image, this is how you could use the docker container runtime
> (LinuxContainerExecutor must be in use and the docker daemon needs to be
> running) :
> {code}
> export
> YARN_EXAMPLES_JAR=./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar
> bin/yarn jar $YARN_EXAMPLES_JAR pi
> -Dmapreduce.map.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dyarn.app.mapreduce.am.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
>
> -Dmapreduce.reduce.env="YARN_CONTAINER_RUNTIME_TYPE=docker,YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=ashahab/hadoop-trunk"
> 4 1000
> {code}
>
> LinuxContainerExecutor can delegate to either runtime on a per container
> basis. If the docker container type is selected, LinuxContainerExecutor
> delegates to the DockerContainerRuntime which in turn uses docker support in
> the container-executor binary to launch/manage docker containers ( see
> YARN-3852 ) .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
