hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-4617) LeafQueue#pendingOrderingPolicy should always use fixed ordering policy instead of using same as active applications ordering policy
Date Thu, 21 Jan 2016 04:04:39 GMT
Rohith Sharma K S created YARN-4617:
---------------------------------------

             Summary: LeafQueue#pendingOrderingPolicy should always use fixed ordering policy
instead of using same as active applications ordering policy
                 Key: YARN-4617
                 URL: https://issues.apache.org/jira/browse/YARN-4617
             Project: Hadoop YARN
          Issue Type: Bug
          Components: capacity scheduler
    Affects Versions: 2.8.0
            Reporter: Rohith Sharma K S
            Assignee: Rohith Sharma K S


In discussion with [~leftnoteasy] in the JIRA [comment|https://issues.apache.org/jira/browse/YARN-4479?focusedCommentId=15108236&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15108236]
pointed out that {{LeafQueue#pendingOrderingPolicy}} should NOT be assumed to be same as active
applications ordering policy. It causes an issue when using fair ordering policy.
Expectations of this JIRA should include
# Create FifoOrderingPolicyForPendingApps which extends FifoOrderingPolicy.
# Comparator of new ordering policy should use RecoveryComparator,PriorityComparator and Fifocomparator
in order respectively.
# Clean up {{LeafQueue#pendingOPForRecoveredApps}} which is no more required once new fixed
ordering policy is created pending applications.




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

Mime
View raw message