ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8591) Configs: Enabling Yarn RM HA through Ambari should enable work preserving RM restart
Date Mon, 08 Dec 2014 20:11:12 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Lysnichenko updated AMBARI-8591:
---------------------------------------
    Attachment: AMBARI-8591.patch

> Configs: Enabling Yarn RM HA through Ambari should enable work preserving RM restart
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8591
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8591
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8591.patch
>
>
> Ambari deploy's Yarn RM HA and does not enable work preserving restarts. Which control
how many time am can restart are not set accounting for HA cluster.
> mapred-site.xml -> mapreduce.am.max-attempts (defaults to 2)
> tez-site.xml -> tez.am.max.app.attempts (defaults to 2)
> yarn-site.xml -> yarn.resourcemanager.am.max-attempts (defaults to 2)
> In gsInstaller we set this all to 20 which might be over kill but i think when yarn HA
is enabled we should set these to a better value. Yarn team should provide input on what we
should set them if HA is on and if they should be different if WRP is on as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message