[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381000#comment-15381000 ]
Arun Suresh commented on YARN-4888: ----------------------------------- Ping [~leftnoteasy], [~jianhe], [~kasha]... Wondering if we can get a review to validate the approach for before we attempt to fix all the checkstyle and javadoc warning As [~subru] mentioned [here|https://issues.apache.org/jira/browse/YARN-4888?focusedCommentId=15380355&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15380355], Please do not be put off by the size of the patch :), Almost all the modifications are a result of directly replacing {{Priority}} with the {{SchedulerKey}} and are very straightforward. > Changes in RM AppSchedulingInfo for identifying resource-requests explicitly > ---------------------------------------------------------------------------- > > Key: YARN-4888 > URL: https://issues.apache.org/jira/browse/YARN-4888 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Subru Krishnan > Assignee: Subru Krishnan > Attachments: YARN-4888-WIP.patch, YARN-4888-v0.patch, > YARN-4888.001.patch > > > YARN-4879 puts forward the notion of identifying allocate requests > explicitly. This JIRA is to track the changes in RM app scheduling data > structures to accomplish it. Please refer to the design doc in the parent > JIRA for details. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org