Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Fri, 13 Sep 2013 17:41:51 +0000 (UTC)
From: "Bikas Saha (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12668400.1379035177268.130424.1379094111975@arcas>
In-Reply-To: <JIRA.12668400.1379035177268@arcas>
References: <JIRA.12668400.1379035177268@arcas>
Subject: [jira] [Resolved] (YARN-1193) ResourceManger.clusterTimeStamp
 should be reset when RM transitions to active
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bikas Saha resolved YARN-1193.
------------------------------

    Resolution: Duplicate
      Assignee:     (was: Karthik Kambatla)

YARN-1027 fixes this.
                
> ResourceManger.clusterTimeStamp should be reset when RM transitions to active
> -----------------------------------------------------------------------------
>
>                 Key: YARN-1193
>                 URL: https://issues.apache.org/jira/browse/YARN-1193
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Karthik Kambatla
>         Attachments: yarn-1193-1.patch
>
>
> ResourceManager.clusterTimeStamp is used to generate application-ids. 
> Currently, when the RM transitions to active-standby-active back and forth, the clusterTimeStamp stays the same leading to apps getting the same ids as jobs from before. This leads to other races in staging directory etc.
> To avoid this, it is better to set it on every transition to Active.

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