Jon Bringhurst created YARN-2093:
------------------------------------

             Summary: Fair Scheduler IllegalStateException after upgrade from 
2.2.0 to 2.4.1-SNAP
                 Key: YARN-2093
                 URL: https://issues.apache.org/jira/browse/YARN-2093
             Project: Hadoop YARN
          Issue Type: Bug
    Affects Versions: 2.4.1
            Reporter: Jon Bringhurst


After upgrading from 2.2.0 to 2.4.1-SNAP, I ran into the following on startup:

{noformat}
21:19:34,308  INFO RMAppAttemptImpl:659 - appattempt_1400092144371_0003_000009 
State change from SUBMITTED to SCHEDULED
21:19:34,309  INFO RMAppAttemptImpl:659 - appattempt_1400092144371_0004_000008 
State change from SUBMITTED to SCHEDULED
21:19:34,310  INFO RMAppAttemptImpl:659 - appattempt_1400092144371_0003_000010 
State change from SUBMITTED to SCHEDULED
21:19:34,310  INFO RMAppAttemptImpl:659 - appattempt_1400092144371_0003_000011 
State change from SUBMITTED to SCHEDULED
21:19:34,317  INFO FairScheduler:673 - Added Application Attempt 
appattempt_1400092144371_0004_000009 to scheduler from user: 
samza-perf-playground
21:19:34,318  INFO FairScheduler:673 - Added Application Attempt 
appattempt_1400092144371_0004_000010 to scheduler from user: 
samza-perf-playground
21:19:34,318  INFO RMAppAttemptImpl:659 - appattempt_1400092144371_0004_000009 
State change from SUBMITTED to SCHEDULED
21:19:34,318  INFO FairScheduler:733 - Application 
appattempt_1400092144371_0003_000005 is done. finalState=FAILED
21:19:34,319  INFO RMAppAttemptImpl:659 - appattempt_1400092144371_0004_000010 
State change from SUBMITTED to SCHEDULED
21:19:34,319  INFO AppSchedulingInfo:108 - Application 
application_1400092144371_0003 requests cleared
21:19:34,319  INFO FairScheduler:673 - Added Application Attempt 
appattempt_1400092144371_0004_000011 to scheduler from user: 
samza-perf-playground
21:19:34,320  INFO FairScheduler:733 - Application 
appattempt_1400092144371_0003_000006 is done. finalState=FAILED
21:19:34,320  INFO AppSchedulingInfo:108 - Application 
application_1400092144371_0003 requests cleared
21:19:34,320  INFO RMAppAttemptImpl:659 - appattempt_1400092144371_0004_000011 
State change from SUBMITTED to SCHEDULED
21:19:34,323 FATAL ResourceManager:600 - Error in handling event type 
APP_ATTEMPT_REMOVED to the scheduler
java.lang.IllegalStateException: Given app to remove 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerApp@429f809d
 does not exist in queue [root.samza-perf-playground, demand=<memory:0, 
vCores:0>, running=<memory:0, vCores:0>, share=<memory:368640, vCores:0>, 
w=<memory weight=1.0, cpu weight=1.0>]
        at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSLeafQueue.removeApp(FSLeafQueue.java:93)
        at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.removeApplicationAttempt(FairScheduler.java:774)
        at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1201)
        at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:122)
        at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:591)
        at java.lang.Thread.run(Thread.java:744)
21:19:34,330  INFO ResourceManager:604 - Exiting, bbye..
21:19:34,335  INFO log:67 - Stopped 
selectchannelconnec...@eat1-app587.stg.linkedin.com:8088
21:19:34,437  INFO Server:2398 - Stopping server on 8033
21:19:34,438  INFO Server:694 - Stopping IPC Server listener on 8033
{noformat}

Last commit message is (branch-2.4 on github.com/apache/hadoop-common):

{noformat}
commit 09e24d5519187c0db67aacc1992be5d43829aa1e
Author: Arpit Agarwal <a...@apache.org>
Date:   Tue May 20 20:18:46 2014 +0000

    HADOOP-10562. Fix CHANGES.txt entry again
    
    git-svn-id: 
https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2.4@1596389 
13f79535-47bb-0310-9956-ffa450edef68
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to