[
https://issues.apache.org/jira/browse/SAMZA-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537094#comment-14537094
]
TJ Giuli commented on SAMZA-519:
--------------------------------
[~jonbringhurst], are you setting the HADOOP_CONF_DIR environment variable to
point to your site's YARN configuration before running run-job.sh? Most likely
it should be /etc/hadoop/conf. We just deployed HA YARN in our cluster and all
of a sudden we could not get our Samza jobs started. We are running CDH5.3.2
and we resolved the issue by setting HADOOP_CONF_DIR to /etc/hadoop/conf. See
http://samza.apache.org/learn/tutorials/0.9/deploy-samza-to-CDH.html
I think you did find a bug in ClientHelper.scala in that it will incorrectly
print out the wrong ResourceManager, but if you have a properly set up
yarn-site.xml config file that Samza can access, YarnClient should handle HA.
> 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.10.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)
