[ https://issues.apache.org/jira/browse/TEZ-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743999#comment-13743999
]
Siddharth Seth commented on TEZ-344:
------------------------------------
bq. allocatedResources now counts resources until exited and released at the RM, right?
No, it counts resources until the scheduler releases them; except for the case where the RM
releases a running container.
Adding a few more comments on the sync, also fixed a couple of typos. Uploading a new patch
and committing. Thanks for the review.
> 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.3.txt, TEZ-344.4.txt, TEZ-344.5.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
time.
> 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
|