[
https://issues.apache.org/jira/browse/SAMZA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Riccomini resolved SAMZA-182.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.7.0
Assignee: Chris Riccomini
Merged and committed.
> 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
> Assignee: Chris Riccomini
> Fix For: 0.7.0
>
> Attachments: SAMZA-182.0.patch, SAMZA-182.1.patch,
> 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)
