[jira] [Reopened] (YARN-5938) Refactoring OpportunisticContainerAllocator use SchedulerRequestKey instead of Priority

["Arun Suresh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun Suresh reopened YARN-5938:
-------------------------------

Reopening to run against trunk

> Refactoring OpportunisticContainerAllocator use SchedulerRequestKey instead of Priority
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-5938
>                 URL: https://issues.apache.org/jira/browse/YARN-5938
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>             Fix For: 3.0.0-beta1
>
>         Attachments: YARN-5938-YARN-5085.001.patch, YARN-5938-YARN-5085.002.patch, YARN-5938-YARN-5085.003.patch, YARN-5938-YARN-5085.004.patch, YARN-5938.001.patch, YARN-5938.002.patch
>
>
> Minor code re-organization to do the following:
> # The OpportunisticContainerAllocatorAMService currently allocates outside the ApplicationAttempt lock maintained by the ApplicationMasterService. This should happen inside the lock.
> # Refactored out some code to simplify the allocate() method.
> # Removed some unused fields inside the OpportunisticContainerAllocator.
> # Re-organized some of the code in the OpportunisticContainerAllocatorAMService::allocate method to make it a bit more readable.
> # Moved SchedulerRequestKey to a new package, so it can be used by the OpportunisticContainerAllocator/Context.
> # Moved all usages of Priority in the OpportunisticContainerAllocator -> SchedulerRequestKey. 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org