[
https://issues.apache.org/jira/browse/HIVE-14397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402503#comment-15402503
]
Sergey Shelukhin commented on HIVE-14397:
-----------------------------------------
Which part of the patch fixes the problem where "when we run more queries the
reopened sessions are not used instead new session is opened"?
Queue name logic makes sense to me
> Queries launched after reopening of tez session launches additional sessions
> ----------------------------------------------------------------------------
>
> Key: HIVE-14397
> URL: https://issues.apache.org/jira/browse/HIVE-14397
> Project: Hive
> Issue Type: Bug
> Components: Tez
> Affects Versions: 2.1.0, 2.2.0
> Reporter: Takahiko Saito
> Assignee: Prasanth Jayachandran
> Priority: Critical
> Attachments: HIVE-14397.1.patch
>
>
> Say we have configured hive.server2.tez.default.queues with 2 queues q1 and
> q2 with default expiry interval of 5 mins.
> After 5 mins of non-usage the sessions corresponding to queues q1 and q2 will
> be expired. When new set of queries are issue after this expiry, the default
> sessions backed by q1 and q2 and reopened again. Now when we run more queries
> the reopened sessions are not used instead new session is opened.
> At this point there will be 4 sessions running (2 abandoned sessions and 2
> current sessions).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
