Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.1.0
-
None
Description
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:
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)