Request failed with status code 504

134 views
Skip to first unread message

AdsA

unread,
Jun 8, 2020, 10:07:09 AM6/8/20
to Druid User
Large queries time out after exactly 1 minute with error “Request failed with status code 504”. How do I fix this? Is there a specific config change I can make?
Cheers

Surekha Saharan

unread,
Jun 8, 2020, 12:32:54 PM6/8/20
to druid...@googlegroups.com
Hi,

You can set the default query timeout by setting druid.server.http.defaultQueryTimeout and it can be overridden by setting timeout value in each query context.
Also, check this article for more tunings around queries returning large result set : https://support.imply.io/hc/en-us/articles/360034310953-Tuning-Druid-for-Large-Result-Sets

HTH
Surekha

On Mon, Jun 8, 2020 at 7:07 AM AdsA <adamada...@gmail.com> wrote:
Large queries time out after exactly 1 minute with error “Request failed with status code 504”. How do I fix this? Is there a specific config change I can make?
Cheers

--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/962bf276-b772-4e97-9569-9b3396f35ba0o%40googlegroups.com.

AdsA

unread,
Jun 9, 2020, 5:37:17 AM6/9/20
to Druid User
Thanks for the reply!
I have tried setting this in the broker as recommenced in the link, as well as trying the historical and common, and it still times out after 1 minute - I notice the default for this value is 300000 millis (5 mins) anyway, so I’m not sure what’s causing a 1 minute timeout.
I am using sql to query, rather than native Druid queries - not sure if this would make any difference?
Cheers!

On Monday, June 8, 2020 at 5:32:54 PM UTC+1, Surekha Saharan wrote:
> Hi,
>
>
> You can set the default query timeout by setting druid.server.http.defaultQueryTimeout and it can be overridden by setting timeout value in each query context.
> Also, check this article for more tunings around queries returning large result set : https://support.imply.io/hc/en-us/articles/360034310953-Tuning-Druid-for-Large-Result-Sets
>
>
> HTH
> Surekha
>
>
> On Mon, Jun 8, 2020 at 7:07 AM AdsA <adamada...@gmail.com> wrote:
> Large queries time out after exactly 1 minute with error “Request failed with status code 504”. How do I fix this? Is there a specific config change I can make?
>
> Cheers
>
>
>
> --
>
> You received this message because you are subscribed to the Google Groups "Druid User" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an email to druid...@googlegroups.com.

Surekha Saharan

unread,
Jun 9, 2020, 1:49:51 PM6/9/20
to druid...@googlegroups.com
Sql queries should not cause a different timeout, are you using the Druid web console to query ? And the sql query would get planned into a native query internally, you can try to set the timeout in the query context. Also check the broker logs to see what's happening.

To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/55c98410-f426-453d-9dff-236ed6ed068do%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages