[
https://issues.apache.org/jira/browse/TEZ-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061824#comment-14061824
]
Gopal V commented on TEZ-1269:
------------------------------
I wonder if hive is doing something to its local resources during queries.
I see " Releasing unused container: container_1405212233811_0251_01_000003"
messages when I reconnect to a HiveServer2 session.
The message clearly says
{code}
YarnTaskSchedulerService: Releasing held container as either there are pending
but unmatched requests or this is not a session,
containerId=container_1405212233811_0251_01_000003, pendingTasks=true,
isSession=true. isNew=false
2014-07-15 01:09:57,954 INFO [DelayedContainerManager]
org.apache.tez.dag.app.rm.YarnTaskSchedulerService: Releasing unused container:
container_1405212233811_0251_01_000003
{code}
> 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)
