[jira] [Commented] (TEZ-2668) Enhancements to TaskScheduler and TaskSchedulerContext APIs

["Siddharth Seth (JIRA)" <ji...@apache.org>]

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

Siddharth Seth commented on TEZ-2668:
-------------------------------------

Also.
// appShutdownRequested not relevant to non YARN schedulers / non centrally managed schedulers
// secretKey in setApplicaitonRegistrationData not always relevant.
// getAppTrackingURL
// containerBeingReleased - should not be required
// Move hasUnregistered from TaskScheduler to TaskSchedulerContext as a setHasUnregistered

> Enhancements to TaskScheduler and TaskSchedulerContext APIs
> -----------------------------------------------------------
>
>                 Key: TEZ-2668
>                 URL: https://issues.apache.org/jira/browse/TEZ-2668
>             Project: Apache Tez
>          Issue Type: Sub-task
>    Affects Versions: TEZ-2003
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>
> Some of the required enhancements
> TaskScheduler
>   // - Should setRegister / unregister be part of APIs when not YARN specific ?
>   // - Include vertex / task information in therequest so that the scheduler can make decisions
>   // around prioritizing tasks in the same vertex when others exist at the same priority.
> TaskSchedulerContext
>   // - setApplicationRegistrationData may not be relevant to non YARN clusters
>   // - getAppFinalStatus may not be relevant to non YARN clusters



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