Hey All, By any chance is there any limitation tha...
# general
p
Hey All, By any chance is there any limitation that number only a certain number of requests can be hit at the same time in druid?
k
There could be a limited number of concurrent connections depending on your config - have a look at https://druid.apache.org/docs/latest/configuration/#server-configuration
p
I don’t see anything given like this in config, also there is no default value given in docs, so what can it be?
Since I have faced intermittent challenges while retreating so trying to figure out can it be due to number of requests hitting druid at the same time
k
So the default is
Copy code
max(10, (Number of cores * 17) / 16 + 2) + 30
but this would not cause the broker to reject queries (HTTP 429). What issue are you seeing? The beginning of this blog post has some details about how the brokers handle this: https://medium.com/@kyle.hoondert/query-laning-in-apache-druid-80cf138806f3
p
I am getting 500 Internal server error, anyway to track or debug this? There are multiple queries hitting at the same time, so I am suspecting it may be due to that. However while I tried it using thread pool executor I am not able to see this
k
oh - a 500 is different - see if you can see anything in your router or broker logs
p
Can you help me to understand the parameter - enableParallelMerge
Anyone?
p
So my doubt here is, if I run the 2-3 different queries at the same time, is there a possibility that results getting mixed with this option enabled?
l
nope
is there any inclination towards parallel merge being the cause of 500?
p
Yes, We are trying to hit two different API calls at the same time but receiving the response of one in another
Although druid from its own giving the response, but in the way it is expecyed
l
Druid merges the results in multiple places, therefore I was curious about the parallel merge being a suspect here.
p
Also a couple of times I saw connection has been shut down, any log where I can see the complete log?
I tried checking broker log, couldn’t find anything useful
l
you can enable debug logging, though I suspect that would be too verbose
p
Yes only thing that made me asked this question was enableParallelMerge parameter
l
idt parallel merge should be the culprit. You can disable it from the config and check the results
p
Sure
How do we enable log debugging?
I would like to try that too