You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Alex Rodoni (Jira)" <ji...@apache.org> on 2019/08/28 21:58:03 UTC
[jira] [Reopened] (IMPALA-8701) Document idle session management
after IMPALA-7802
[ https://issues.apache.org/jira/browse/IMPALA-8701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rodoni reopened IMPALA-8701:
---------------------------------
> Document idle session management after IMPALA-7802
> --------------------------------------------------
>
> Key: IMPALA-8701
> URL: https://issues.apache.org/jira/browse/IMPALA-8701
> Project: IMPALA
> Issue Type: Task
> Components: Docs
> Affects Versions: Impala 3.3.0
> Reporter: Michael Ho
> Assignee: Alex Rodoni
> Priority: Major
> Labels: future_release_doc, in_33
> Fix For: Impala 3.3.0
>
>
> After IMPALA-7802 is fixed, the network connection of an idle session will be closed {{\-\-idle_client_poll_time_s}} seconds latest after the session has been declared idle. This is a change of behavior from previous versions in which the client connection will hang around until the user explicitly closes the session and disconnects.
> By default, {{\-\-idle_client_poll_time_s}} is set to 30 seconds and the previous behavior can be restored by setting to 0. In addition, the session will only be closed if idle session timeout has been configured to be greater than 0 for the session either via the startup flag {{--idle_session_timeout}} or the query option {{IDLE_SESSION_TIMEOUT}}. If idle session timeout is not configured, a session cannot become idle by definition and therefore its connection cannot be closed until the client explicitly closes it.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org