I've looked at the log files and what I see is that Drillbit becomes
unable to maintain its end of the JDBC connection to CLI that you're
working in.
You can try to set drill.exec.rpc.user.timeout to 0 in
drill-override.conf, which will disable the relevant timeout. Disabling
this timeout isn't any kind of solution, just a way to keep the query
running while you look at what's making the Drillbit unresponsive. My
bet is that physical RAM is being exhausted causing the OS to start
heavy paging of data to swap space. If you look at OS RAM and swap
metrics while the query is running it should be clear if this is this case.
If it is the case then it is probably better to let Drill's hash join
spill data to disk itself than it is to oversubscribe physical memory
and force the OS to swap (e.g. by setting too big a number in a variable
like DRILLBIT_MAX_PROC_MEM).
Regards
James
On 2023/10/13 10:31, muhl...@ntokoto.co.za wrote:
Hi,
Let me regenerate the error again I will share the log file once done.
I have 3 log file:
Which one of those I must share:
sqlline.log
sqlline.log.1
sqlline_queries.log
Files are a bit big, Which email can I use to share the bigger files?
Regards,
Muhluri
-----Original Message-----
From: James Turton <dz...@apache.org>
Sent: Friday, 13 October 2023 10:16
To: user@drill.apache.org; muhl...@ntokoto.co.za
Subject: Re: ChannelClosedException
Going further, it looks like your entire Drillbit is crashing so this is
something severe, perhaps an out-of-memory situation. The sqlline.log file
should provide some clues.
On 2023/10/13 09:53, James Turton wrote:
The errors that reach the surface in the embedded Drill CLI do not
include all of the errors logged by Drill server processes. Please
look for the file sqlline.log which by default will be in the log/
subdirectory of your Drill installation...
On 2023/10/12 15:03, muhl...@ntokoto.co.za wrote:
Hi,
I am running from the drill console, The application I want to use it
on is QuerySurge. I am getting the same error message in both platforms.
Regards,
Muhluri
-----Original Message-----
From: James Turton <dz...@apache.org>
Sent: Thursday, 12 October 2023 13:43
To: muhl...@ntokoto.co.za
Subject: Re: ChannelClosedException
Also, please look in the Drillbit logs. The query may be encountering
invalid data and failing when you remove your LIMIT clause. Are you
using DBeaver to submit your queries btw? That error looks familiar...
On 2023/10/10 15:58, Charles Givre wrote:
Hi Desmond,
Can you share a bit more? What version of Drill are you running?
Java? etc. What data are you trying to query?
Best,
-- C
On Oct 10, 2023, at 2:02 AM, <muhl...@ntokoto.co.za>
<muhl...@ntokoto.co.za> wrote:
Hi Team,
When I run a Query for a limited number of records it returns the
results.
When I remove the limit on the Query it fails with below error. May
you please assist.
Exception: SQL_EXCEPTION java.sql.SQLException: CONNECTION ERROR:
Connection <--> (user client) closed unexpectedly. Drillbit down?
[Error Id:
fba8461f-c896-4c56-b617-1625361e577d ]
Regards,
Muhluri
