[ https://issues.apache.org/jira/browse/PHOENIX-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Antal updated PHOENIX-5810: ----------------------------------- Attachment: PHOENIX-5810.master.v4.patch > 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)