[
https://issues.apache.org/jira/browse/SAMZA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931953#comment-13931953
]
ASF GitHub Bot commented on SAMZA-182:
--------------------------------------
GitHub user esetnik opened a pull request:
https://github.com/apache/incubator-samza/pull/4
Adds RM hostname specification in YarnConfig
See https://issues.apache.org/jira/browse/SAMZA-182
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/esetnik/incubator-samza yarn_remote_rm
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-samza/pull/4.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4
----
commit a4697883dd3c9f498a48f57f19df0de2dac9a4e3
Author: Ethan Setnik <[email protected]>
Date: 2014-03-12T16:31:35Z
Adds RM hostname specification in YarnConfig
----
> RM Hostname Specification For SamzaAppMaster
> --------------------------------------------
>
> Key: SAMZA-182
> URL: https://issues.apache.org/jira/browse/SAMZA-182
> Project: Samza
> Issue Type: Improvement
> Components: yarn
> Affects Versions: 0.7.0
> Reporter: Ethan Setnik
> Attachments: yarn_remote_rm.patch
>
>
> When running Samza in a clustered environment, I found that SamzaAppMaster
> jobs running on remote Yarn NodeManagers do not know how to properly contact
> the ResourceManager.
> I have included a small patch that adds a directive to the YarnConfig to
> specify the hostname of the RM via "yarn.rm.hostname". I have tested this
> directive and it is working in my environment.
> Please take a look at the patch and provide advise on whether this is the
> correct approach. If there is no better suggestion, i'd be happy to writeup
> some test cases to support the patch.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
