[jira] [Commented] (TEZ-1665) DAGScheduler should provide a priority range instead of an exact priority

["Bikas Saha (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TEZ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171709#comment-14171709 ] 

Bikas Saha commented on TEZ-1665:
---------------------------------

[~hitesh] [~sseth] please review.

> DAGScheduler should provide a priority range instead of an exact priority
> -------------------------------------------------------------------------
>
>                 Key: TEZ-1665
>                 URL: https://issues.apache.org/jira/browse/TEZ-1665
>             Project: Apache Tez
>          Issue Type: Task
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: TEZ-1665.1.patch
>
>
> Specifying the exact priority leaks task attempt concepts into the DAGScheduler. Eg. the DAGScheduler increases the priority of attempt-re-executions arbitrarily. Providing a range allows these decisions to be made at the task attempt level. e.g. when there are no competing tasks then there is no reason to increase the priority. Similarly for speculation, the speculative task priority could be lower than normal tasks because we may want the first attempt of other tasks to run ahead of a speculative task. These relative priorities within a vertex can be made locally instead of leaking into the DAGScheduler.



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