[
https://issues.apache.org/jira/browse/YARN-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922596#comment-13922596
]
Hudson commented on YARN-1785:
------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1718 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1718/])
YARN-1785. FairScheduler treats app lookup failures as ERRORs. (bc Wong via
kasha) (kasha:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1574604)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
> FairScheduler treats app lookup failures as ERRORs
> --------------------------------------------------
>
> Key: YARN-1785
> URL: https://issues.apache.org/jira/browse/YARN-1785
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: bc Wong
> Assignee: bc Wong
> Fix For: 2.4.0
>
> Attachments:
> 0001-YARN-1785.-FairScheduler-treats-app-lookup-failures-.patch
>
>
> When invoking the /ws/v1/cluster/apps endpoint, RM will eventually get to
> RMAppImpl#createAndGetApplicationReport, which calls
> RMAppAttemptImpl#getApplicationResourceUsageReport, which looks up the app in
> the scheduler, which may or may not exist. So FairScheduler shouldn't log an
> error for every lookup failure:
> {noformat}
> 2014-02-17 08:23:21,240 ERROR
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler:
> Request for appInfo of unknown attemptappattempt_1392419715319_0135_000001
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
