hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms
Date Tue, 25 Jun 2013 01:20:21 GMT

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

Karthik Kambatla updated YARN-884:
----------------------------------

    Attachment: yarn-884-1.patch

Uploading a straight-forward patch.
                
> AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-884
>                 URL: https://issues.apache.org/jira/browse/YARN-884
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.0.4-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>              Labels: configuration
>         Attachments: yarn-884-1.patch
>
>
> As the AM can't outlive the NM on which it is running, it is a good idea to disallow
setting the am.liveness-monitor.expiry-interval-ms to a value higher than nm.liveness-monitor.expiry-interval-ms

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message