[
https://issues.apache.org/jira/browse/HIVE-12674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-12674:
------------------------------------
Attachment: HIVE-12674.patch
The first patch. Still need to test in cluster. I created the subclass for the
session that's part of the pool and most of the expiration logic, as well as
some pool-related logic is in it. This could be further improved, so that the
code elsewhere could avoid e.g. calling pool.close on all the sessions because
it's not clear if the session is coming from the pool.
[~vikram.dixit] can you check if this makes sense?
cc [~sseth]
RB https://reviews.apache.org/r/41431/
> HS2 Tez sessions should have maximum age
> ----------------------------------------
>
> Key: HIVE-12674
> URL: https://issues.apache.org/jira/browse/HIVE-12674
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-12674.patch
>
>
> Certain tokens passed to AM by clients (e.g. an HDFS token) have maximum
> lifetime beyond which they cannot be renewed. We should cycle long-lived
> session AMs after a configurable period to avoid problems with these.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
