impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Apple (JIRA)" <>
Subject [jira] [Updated] (IMPALA-4488) Impala session times out prematurely - even if there is a running query
Date Thu, 16 Mar 2017 03:30:41 GMT


Jim Apple updated IMPALA-4488:
    Attachment: profile.txt

> Impala session times out prematurely - even if there is a running query
> -----------------------------------------------------------------------
>                 Key: IMPALA-4488
>                 URL:
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend, Clients
>    Affects Versions: Impala 2.6.0
>            Reporter: Miklos Szurap
>            Assignee: Henry Robinson
>            Priority: Critical
>             Fix For: Impala 2.8.0
>         Attachments: profile.txt, profile.txt
> Setting --idle_session_timeout to a lower value (for example 60 seconds) may cause queries
to fail (to be cancelled) with "Session expired due to inactivity". 
> Currently we are experiencing this only through 3rd party clients (through Cloudera Impala
ODBC connector), impala-shell and Hue/Impala query editor works well.
> On the ODBC client side the error message is 
> {noformat}
> Oct 20 13:43:41 ERROR 3933976352 Statement::SQLExecDirectW: [Cloudera][ImpalaODBC] (110)
Error while executing a query in Impala: [HY000] : Unknown error and could not get runtime
log: Client session expired due to more than 60s of inactivity (last activity was at: 2016-10-20
> {noformat}
> Based on the [Impala documentation|]
running queries should not be killed because of the "idle session timeout":
> {quote}
> The --idle_session_timeout option specifies the time in seconds after which an idle session
is expired. A session is idle when no activity is occurring for any of the queries in that
session, and the session has not started any new queries.
> {quote}
> To reproduce:
> # Set {{--idle_session_timeout=60}}
> # Set up Cloudera Impala ODBC driver
> # Through a 3rd party ODBC client run a bigger query, lasting longer than the session

This message was sent by Atlassian JIRA

View raw message