You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/09/13 19:41:51 UTC

[jira] [Resolved] (YARN-1193) ResourceManger.clusterTimeStamp should be reset when RM transitions to active

     [ 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