hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subru Krishnan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5601) Make the RM epoch base value configurable
Date Fri, 02 Sep 2016 00:32:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457070#comment-15457070

Subru Krishnan commented on YARN-5601:

The test case failure seems unrelated to the patch.

> 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, YARN-5601-YARN-2915-v2.patch, YARN-5601-YARN-2915-v3.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

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

View raw message