s and what were the memory
> settings that worked for you? That way, others can also benefit from your
> experience.
>
>
>
> -Original Message-
> From: Alan Höng [mailto:alan.f.ho...@gmail.com]
> Sent: Thursday, September 21, 2017 2:25 AM
> To: user@drill.apache.org
>
that worked for you? That way, others can also benefit from your
experience.
-Original Message-
From: Alan Höng [mailto:alan.f.ho...@gmail.com]
Sent: Thursday, September 21, 2017 2:25 AM
To: user@drill.apache.org
Subject: Re: User client timeout with results > 2M rows
It was resolved
ote:
>
>> The client error reported is usually trimmed. What is the stack trace in
>> the drillbit logs? That will tell you exactly where the timeout occurred
>> and make it easier for you to work with.
>>
>> I did a quick browse through for 'S3 Timeout' (
>&
could browse through to see if any suggestions here can help unblock
> you.
>
>
>
> -Original Message-
> From: Alan Höng [mailto:alan.f.ho...@gmail.com]
> Sent: Wednesday, September 20, 2017 12:22 PM
> To: user@drill.apache.org
> Subject: Re: User client timeout with
.html?user@drill.apache.org:gte=1d:%20S3%20timeout
). You could browse through to see if any suggestions here can help unblock you.
-Original Message-
From: Alan Höng [mailto:alan.f.ho...@gmail.com]
Sent: Wednesday, September 20, 2017 12:22 PM
To: user@drill.apache.org
Subject: Re: User client timeout wi
Yes it takes about 2-3min for the timeout to appear the query itself should
finish in that time. The files are not that big for debugging. I have, but
I couldn't find anything relevant or helpful in my situation so far.
On Wed, 20 Sep 2017 at 20:41 Kunal Khatua wrote:
> Do you know in how much
Do you know in how much time does this timeout occur? There might be some
tuning needed to increase a timeout. Also, I think this (S3 specifically) has
been seen before... So you might find a solution within the mailing list
archives. Did you try looking there?
From: Alan Höng
Sent: Wednesday
