tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEZ-344) Support delayed scheduling for re-used containers
Date Thu, 15 Aug 2013 23:46:49 GMT

     [ https://issues.apache.org/jira/browse/TEZ-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Siddharth Seth updated TEZ-344:

    Attachment: TEZ-344.2.txt

Updated patch. Has grown quite a bit. Changes.
- unassignable containers will not be held on to.
- new callback to apps to indicate container release - so that the app can be told about delayed
container releases.
- App callbacks are now handled by a separate Executor - since some calls need to be made
from deep inside a call stack. That contributes a big chunk towards the size increase.
- TEZ-356 should be resolved - using assignedContaienrs as a repository for containers which,
at some point, have run a task, but haven't been released yet.
- A delay value of 0 effectively disables putting anything into the delay queue.
- Couple new unit tests.
> Support delayed scheduling for re-used containers
> -------------------------------------------------
>                 Key: TEZ-344
>                 URL: https://issues.apache.org/jira/browse/TEZ-344
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>              Labels: TEZ-0.2.0
>         Attachments: TEZ-344.2.txt, TEZ-344.wip.txt
> This, for now, is primarily to help with testing of Tez on clusters.
> Would have to go in with a warning since this could cause jobs to hang / run for a long
> Longer term, this can be enhanced to set limits on how long to wait before assigning
non-local tasks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message