[
https://issues.apache.org/jira/browse/DRILL-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701716#comment-14701716
]
Daniel Barclay (Drill) commented on DRILL-3523:
-----------------------------------------------
> After a period of inactivity in the Drill CLI client before issuing another
> statement, it appears to time out the session/connection
After how long a period of inactivity?
Is it after around 30 seconds? It don't think the JDBC connection has an
intentional timeout, but there's an internal heartbeat/keep-alive check at
around 30 seconds that I've seen occur (in my case, when I had the client and
server sides configured inconsistently).)
> and the client returns an error instead of reconnecting to Drill.
Which error/exception message?
> It should instead just implicitly "!reconnect" itself since I can't think of
> a good reason why I have to do this by hand every time.
It needs to at least not reconnect automatically without telling you, since the
server-side state of the connection (e.g., results of USE x, ALTER SESSION ...,
etc.) will be reset. (It would be really confusing if the state reset without
notice why.)
> Drill client CLI does not reconnect to Drillbit after long period of
> inactivity
> -------------------------------------------------------------------------------
>
> Key: DRILL-3523
> URL: https://issues.apache.org/jira/browse/DRILL-3523
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - CLI
> Affects Versions: 1.1.0
> Reporter: Hari Sekhon
> Assignee: Daniel Barclay (Drill)
> Fix For: 1.2.0
>
>
> After a period of inactivity in the Drill CLI client before issuing another
> statement, it appears to time out the session/connection and the client
> returns an error instead of reconnecting to Drill.
> It should instead just implicitly "!reconnect" itself since I can't think of
> a good reason why I have to do this by hand every time.
> Unlike in DRILL-3514 the drillbit in this case was never restarted, although
> the same fix could probably solve both issues.
> The error received when trying to issue a new query after some absence is:
> {code}Error: CONNECTION ERROR: Connection /x.x.x.x:54367 <--> /x.x.x.x:31010
> (user client) closed unexpectedly.
> [Error Id: 68714cc2-65f5-4cac-b062-44331f8f4c31 ] (state=,code=0)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
