[
https://issues.apache.org/jira/browse/TEZ-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061857#comment-14061857
]
Gopal V commented on TEZ-1269:
------------------------------
The issue seems to be that I run a query which takes up 199 containers, it
decays to 20.
Then I run a query which takes up 3 containers - it drops the 20 to allocate 3
new containers.
The swimlane svg attached clearly shows that behaviour - still unexplained.
> TaskScheduler prematurely releases containers
> ---------------------------------------------
>
> Key: TEZ-1269
> URL: https://issues.apache.org/jira/browse/TEZ-1269
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-1269.1.patch, TEZ-1269.2.patch, TEZ-1269.3.patch,
> TEZ-1269.svg
>
>
> It checks for session mode and if not true, and if there are no outstanding
> requests, then it releases the containers before the container timeout has
> expired. If the state machine is on its way to scheduling new tasks during
> this time then they will not be able to reuse these containers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
