You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Alexander Schurman (JIRA)" <ji...@apache.org> on 2015/11/09 12:18:11 UTC

[jira] [Commented] (SAMZA-519) Support for Yarn HA

    [ https://issues.apache.org/jira/browse/SAMZA-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996388#comment-14996388 ] 

Alexander Schurman commented on SAMZA-519:
------------------------------------------

Hello team,

I was recently working with a Customer and this issue was happening, the isue is related to the YARN Master App not managing the HA environment well.

This was PATCHED recently but for the MapReduce Application master, please see it here
https://issues.apache.org/jira/browse/MAPREDUCE-6484

If you see the PATCHED code, you will understand the issue and the resolution maybe for your case


> 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)