[
https://issues.apache.org/jira/browse/SAMZA-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288483#comment-14288483
]
Jon Bringhurst commented on SAMZA-519:
--------------------------------------
Here's an example of potentially problematic code. I'm not familiar enough with
Yarn HA to be sure what the necessary changes should be:
{noformat}
ClientHelper.scala: info("trying to connect to RM %s" format
conf.get(YarnConfiguration.RM_ADDRESS, YarnConfiguration.DEFAULT_RM_ADDRESS))
{noformat}
My guess is that this should use something like
org.apache.hadoop.yarn.conf.HAUtil.getRMHAId().
> Support for Yarn HA
> -------------------
>
> Key: SAMZA-519
> URL: https://issues.apache.org/jira/browse/SAMZA-519
> Project: Samza
> Issue Type: New Feature
> Components: yarn
> Affects Versions: 0.8.1
> Environment: Yarn 2.6.0 - 2 RMs with HA enabled
> Reporter: Jon Bringhurst
> Fix For: 0.9.0
>
>
> Samza appears to have trouble working with Yarn HA.
> The AM starts up, but it tries to connect to 0.0.0.0 instead of the active RM.
> When "yarn.resourcemanager.hostname" is added back into the NM config, the AM
> works again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
