You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Subru Krishnan (JIRA)" <ji...@apache.org> on 2016/08/30 22:43:20 UTC

[jira] [Updated] (YARN-5601) Make the RM epoch base value configurable

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

Subru Krishnan updated YARN-5601:
---------------------------------
    Attachment: YARN-5601-YARN-2915-v1.patch

A simple patch that reads the base epoch value from config with updated tests to validate the same.

> Make the RM epoch base value configurable
> -----------------------------------------
>
>                 Key: YARN-5601
>                 URL: https://issues.apache.org/jira/browse/YARN-5601
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Subru Krishnan
>         Attachments: YARN-5601-YARN-2915-v1.patch
>
>
> Currently the epoch always starts from zero. This can cause container ids to conflict for an application under Federation that spans multiple RMs concurrently. This JIRA proposes to make the RM epoch base value configurable which will allow us to avoid conflicts by setting different values for each RM.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org