[
https://issues.apache.org/jira/browse/YARN-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625163#comment-14625163
]
Wangda Tan commented on YARN-3873:
----------------------------------
Hi [~sunilg],
I can understand the value of supporting customized comparator for pending
applications (for example priority-based activation), but I'm not sure if using
same comparator of orderingPolicy is also valid for pendingApplications.
For example, fair comparator considers demand resources, this may not make
sense when comparing pending applications. It makes more sense to me if we
activate application by its submission order instead of demand (size of AM
container resource request).
How about change the JIRA purpose to be: support customized comparator to
activate applications. You can do this by adding a getActivateIterator to
OrderingPolicy or creating new interface for it.
I also suggest to put this as a sub JIRA of YARN-3306 for better tracking.
Thoughts?
> pendingApplications in LeafQueue should also use OrderingPolicy
> ---------------------------------------------------------------
>
> Key: YARN-3873
> URL: https://issues.apache.org/jira/browse/YARN-3873
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.7.0
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-YARN-3873.patch, 0002-YARN-3873.patch
>
>
> Currently *pendingApplications* in LeafQueue is using
> {{applicationComparator}} from CapacityScheduler. This can be changed and
> pendingApplications can use the OrderingPolicy configured in Queue level
> (Fifo/Fair as configured).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
