This message was deleted.

druid.server.http.defaultQueryTimeout

is the config that controls this and it defaults to 30 seconds (30000 Millis). See: https://druid.apache.org/docs/latest/configuration/index.html#indexer-concurrent-requests You probably want to set this in the common runtime configs as it applies to historicals and brokers as well as middlemanagers/indexers if using streaming. Also if you have a load balancer in front of your brokers or routers you will want to make sure it's set appropriately there as well. You can also override it for specific queries through context settings if you don't want to override the setting globally. See: https://druid.apache.org/docs/latest/querying/query-context.html

oh thank you but isn’t the default value of druid.server.http.defaultQueryTimeout is 300000 milliseconds (300 seconds)

Oh yeah it is 300 seconds (5mins, 300000 millis). Do you have any load balancers or reverse proxies in front of your queries? Do you know if you are getting a timeout from Druid or a network timeout? Sometimes it can be the network or load balancer that also has an idle connection timeout that can interfere if you queries are taking a while before returning the first/next bytes of data.

definetly i would check it out and response