[ 
https://issues.apache.org/jira/browse/IMPALA-8701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891450#comment-16891450
 ] 

ASF subversion and git services commented on IMPALA-8701:
---------------------------------------------------------

Commit 1c9af2cb526b038c080f1b09acc403e8d7378364 in impala's branch 
refs/heads/master from Alex Rodoni
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=1c9af2c ]

IMPALA-8701: [DOCS] Document --idle_client_poll_time_s flag

Change-Id: I32ace786904f564b9c5fa3ed594e2b679b76d5c6
Reviewed-on: http://gerrit.cloudera.org:8080/13896
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Reviewed-by: Michael Ho <k...@cloudera.com>


> 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
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to