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 "Rohith (JIRA)" <ji...@apache.org> on 2014/11/14 22:20:33 UTC

[jira] [Commented] (YARN-2865) Application recovery continuously fails with "Application with id already present. Cannot duplicate"

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

Rohith commented on YARN-2865:
------------------------------

I encountered this scenario in my test cluster strange way!! causing below exception.
{code}
2014-11-14 04:11:33,433 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAppManager: Recovering 2 applications
2014-11-14 04:11:33,433 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAppManager: Default priority level is set to application:application_1415591025732_0001
2014-11-14 04:11:33,433 WARN org.apache.hadoop.yarn.server.resourcemanager.RMAppManager: Application with id application_1415591025732_0001 is already present! Cannot add a duplicate!
2014-11-14 04:11:33,433 ERROR org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Failed to load/recover state
org.apache.hadoop.yarn.exceptions.YarnException: Application with id application_1415591025732_0001 is already present! Cannot add a duplicate!
                at org.apache.hadoop.yarn.ipc.RPCUtil.getRemoteException(RPCUtil.java:45)
                at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.createAndPopulateNewRMApp(RMAppManager.java:364)
                at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recoverApplication(RMAppManager.java:332)
                at org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recover(RMAppManager.java:436)
                at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.recover(ResourceManager.java:1146)
                at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMActiveServices.serviceStart(ResourceManager.java:521)
                at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
                at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.startActiveServices(ResourceManager.java:925)
                at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$1.run(ResourceManager.java:966)
                at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$1.run(ResourceManager.java:962)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.Subject.doAs(Subject.java:415)
                at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1612)
                at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.transitionToActive(ResourceManager.java:962)
                at org.apache.hadoop.yarn.server.resourcemanager.AdminService.transitionToActive(AdminService.java:281)
                at org.apache.hadoop.yarn.server.resourcemanager.EmbeddedElectorService.becomeActive(EmbeddedElectorService.java:126)
                at org.apache.hadoop.ha.ActiveStandbyElector.becomeActive(ActiveStandbyElector.java:805)
                at org.apache.hadoop.ha.ActiveStandbyElector.processResult(ActiveStandbyElector.java:416)
                at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:602)
                at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498)
{code}

> Application recovery continuously fails with "Application with id already present. Cannot duplicate"
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2865
>                 URL: https://issues.apache.org/jira/browse/YARN-2865
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Rohith
>            Assignee: Rohith
>
> YARN-2588 handles exception thrown while transitioningToActive and reset activeServices. But it misses out clearing RMcontext apps/nodes details and ClusterMetrics and QueueMetrics. This causes application recovery to fail.  



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