[
https://issues.apache.org/jira/browse/PHOENIX-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074683#comment-17074683
]
Hadoop QA commented on PHOENIX-5810:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12998739/PHOENIX-5810.master.v4.patch
against master branch at commit 40bcc0184d3f7257ba2ce98b045d6e8a41f58a00.
ATTACHMENT ID: 12998739
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3714//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3714//console
This message is automatically generated.
> PhoenixMRJobSubmitter is not working on a cluster with a single yarn RM
> -----------------------------------------------------------------------
>
> Key: PHOENIX-5810
> URL: https://issues.apache.org/jira/browse/PHOENIX-5810
> Project: Phoenix
> Issue Type: Bug
> Reporter: Richard Antal
> Assignee: Richard Antal
> Priority: Major
> Attachments: PHOENIX-5810.master.v1.patch,
> PHOENIX-5810.master.v2.patch, PHOENIX-5810.master.v3.patch,
> PHOENIX-5810.master.v4.patch
>
>
> {code:java}
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode =
> NoNode for /yarn-leader-election{code}
> The error happens when we want to run scheduleIndexBuilds. In
> getSubmittedYarnApps, getActiveResourceManagerHost uses zookeeper to
> determine the active Resource Manager.
> But /yarn-leader-election only exists if yarn is in HA mode.
> I think this function should work well when we have single yarn RM and read
> its address from the config.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
