You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2015/07/30 22:21:04 UTC
[jira] [Updated] (TEZ-2666) Enhancements to TaskCommunicator and
TaskCommunicatorContext interface
[ https://issues.apache.org/jira/browse/TEZ-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated TEZ-2666:
--------------------------------
Description:
TaskCommunicator
// - registerContainerEnd should provide the end reason / possible rename
// - get rid of getAddress
// - Add methods to support task preemption
// - Add a dagStarted notification, along with a payload
TaskCommunicatorContext
// - Consolidate usage of IDs
// - Split the heartbeat API to a liveness check and a status update
// - Rename and consolidate TaskHeartbeatResponse and TaskHeartbeatRequest
// - Fix taskStarted needs to be invoked before launching the actual task.
// - Potentially add methods to report availability stats to the scheduler
// - Report taskSuccess via a method instead of the heartbeat
// - Add methods to signal container / task state changes
// - Maybe add book-keeping as a helper library, instead of each impl tracking container to task etc.
// - Handling of containres / tasks which no longer exist in the system (formalized interface instead of a shouldDie notification)
was:
TaskCommunicator
// - registerContainerEnd should provide the end reason / possible rename
// - get rid of getAddress
// - Add methods to support task preemption
// - Add a dagStarted notification, along with a payload
TaskCommunicatorContext
// - Consolidate usage of IDs
// - Split the heartbeat API to a liveness check and a status update
// - Rename and consolidate TaskHeartbeatResponse and TaskHeartbeatRequest
// - Fix taskStarted needs to be invoked before launching the actual task.
// - Potentially add methods to report availability stats to the scheduler
// - Report taskSuccess via a method instead of the heartbeat
// - Add methods to signal container / task state changes
// - Maybe add book-keeping as a helper library, instead of each impl tracking container to task etc.
> Enhancements to TaskCommunicator and TaskCommunicatorContext interface
> ----------------------------------------------------------------------
>
> Key: TEZ-2666
> URL: https://issues.apache.org/jira/browse/TEZ-2666
> Project: Apache Tez
> Issue Type: Sub-task
> Affects Versions: TEZ-2003
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
>
> TaskCommunicator
> // - registerContainerEnd should provide the end reason / possible rename
> // - get rid of getAddress
> // - Add methods to support task preemption
> // - Add a dagStarted notification, along with a payload
> TaskCommunicatorContext
> // - Consolidate usage of IDs
> // - Split the heartbeat API to a liveness check and a status update
> // - Rename and consolidate TaskHeartbeatResponse and TaskHeartbeatRequest
> // - Fix taskStarted needs to be invoked before launching the actual task.
> // - Potentially add methods to report availability stats to the scheduler
> // - Report taskSuccess via a method instead of the heartbeat
> // - Add methods to signal container / task state changes
> // - Maybe add book-keeping as a helper library, instead of each impl tracking container to task etc.
> // - Handling of containres / tasks which no longer exist in the system (formalized interface instead of a shouldDie notification)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)