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

Szilard Nemeth commented on YARN-6964:
--------------------------------------

Hi [~templedf]!

Thanks for the updated patch. LGTM, findbugs issue is unrelated (this is a 
known issue, we have a Jira for fixing this).

Looking at the unit test failure, I don't get why we have the compilation 
error: 
{code:java}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project hadoop-yarn-server-resourcemanager: Compilation failure
[ERROR] 
/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerApplicationAttempt.java:[1296,25]
 error: cannot find symbol
{code}
Any idea?

Thanks!

 

> Fair scheduler misuses Resources operations
> -------------------------------------------
>
>                 Key: YARN-6964
>                 URL: https://issues.apache.org/jira/browse/YARN-6964
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 3.0.0-alpha4
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>            Priority: Major
>         Attachments: YARN-6964.001.patch, YARN-6964.002.patch, 
> YARN-6964.003.patch, YARN-6964.004.patch, YARN-6964.005.patch, 
> YARN-6964.006.patch, YARN-6964.007.patch, YARN-6964.008.patch, 
> YARN-6964.009.patch, YARN-6964.010.patch, YARN-6964.011.patch, 
> YARN-6964.012.patch
>
>
> There are several places where YARN uses the {{Resources}} class to do 
> comparisons of {{Resource}} instances incorrectly.  This patch corrects those 
> mistakes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to