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.