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

Hadoop QA commented on YARN-2657:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12673697/YARN-2567-001.patch
  against trunk revision 853cb70.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5331//console

This message is automatically generated.

> MiniYARNCluster to (optionally) add MicroZookeeper service
> ----------------------------------------------------------
>
>                 Key: YARN-2657
>                 URL: https://issues.apache.org/jira/browse/YARN-2657
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-2567-001.patch
>
>
> This is needed for testing things like YARN-2646: add an option for the 
> {{MiniYarnCluster}} to start a {{MicroZookeeperService}}.
> This is just another YARN service to create and track the lifecycle. The 
> {{MicroZookeeperService}} publishes its binding information for direct takeup 
> by the registry services...this can address in-VM race conditions.
> The default setting for this service is "off"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to