You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Botong Huang (JIRA)" <ji...@apache.org> on 2017/12/20 18:55:00 UTC

[jira] [Created] (YARN-7676) Fix inconsistent priority ordering in Priority and SchedulerRequestKey

Botong Huang created YARN-7676:
----------------------------------

             Summary: Fix inconsistent priority ordering in Priority and SchedulerRequestKey
                 Key: YARN-7676
                 URL: https://issues.apache.org/jira/browse/YARN-7676
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Botong Huang
            Assignee: Botong Huang
            Priority: Minor


Today the priority ordering in _Priority.compareTo()_ and _SchedulerRequestKey.compareTo()_ is inconsistent. Both _compareTo_ method is trying to reverse the order: 

P0.compareTo(P1) > 0, meaning priority wise P0 < P1. However, SK(P0).comapreTo(SK(P1)) < 0, meaning priority wise SK(P0) > SK(P1). 

This is attempting to fix that by undo both reversing logic. So that priority wise P0 > P1 and SK(P0) > SK(P1). 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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