<https://apache-pinot.slack.com/files/U020N9ADN5D/...
# troubleshooting
r

https://apache-pinot.slack.com/files/U020N9ADN5D/F0233EVB6P5/img_20210526_174024.jpg

m
When the query fails, can you run the same query directly to Pinot? Let's first find out if isue is Pinot side or Presto side.
cc @Xiang Fu
r
@Mayank how should I submit 4 queries simentenoulsly with Pinot UI.because this issue I am getting when I was trying to run all the queries same time. If I am running queries seperately then it's working fine.
m
Same queries running separately works fine. or those are different queries?
r
Same queries working fine separately
m
What's the resources (CPU/MEM/HEAP) on pinot vms?
r
I am only facing the issue when I am refreshing the entire dashboard where I used all these four queries.
m
One possibility is that the queries are expensive when run in parallel and your Pinot VMs do not have enough resource to answer the query in parallel.
It is hard to tell from the Presto side stack trace you pasted
r
Hmm any way to check resource allocation in pinot. Queries are also not expensive just taking sum and doing group by on one column. In 2nd query taking count on same group by column. And in 3rd query calculating percentage on same group by column. And I have only 1000 records in table.
m
I am asking about VM size heap size etc. If you are using latest master there's an appConfig endpoint in Swagger.
r
I m on swagger UI where I need to check that
m
Is this latest master, or 0.7.1?
Master has it, 0.7.1 does not have that code yet
for latest master code, just search for
appConfigs
r
appConfigs is not there. I have 0.7 1
m
yeah that code does not have it
you can log on to vm and find the jvm settings and cpu/ram?
r
Ok let me check
m
And also for the individual successful queries, let's see the numDocs/numEntries etc. Then we will know how much work each query is doing and how much resource is there on VM.
r
Ok @Mayank
x
I feel it’s timeout on pinot side?
can you check the queries generated from the superset?
m
Yeah, that's what I am suspecting too.
@Xiang Fu He ran the 4 queries generated, and was able to run them individually
x
you can view it from the right link button when you enter into each chart
ic
m
Only when these queries fired in parallel, that's when this happens.
x
then maybe try to increase pinot server timeout