Hi we are getting a 500 error with no logs when doing querie

Question

Hi we are getting a 500 error with no logs when doing queries with Integer MAX VALUE as the limit on pinot 0 7 1 I see from the code that should be the max limit Is there something else we are running into there are no table quotas Here is the full error redacted hosts and table names to maintain super secrecy ```Unexpected response status 500 for request sql select AAA BBB from CCC limit 2147483647 to url <http XXXX> XXXX query sql with headers Accept= application json Content Type= application json full response null```

Elon · Answer

Should I create a github issue I can also help and work on this lmk

Elon · Answer

The controller has a stack trace but not the broker and there are no logs other than that the request was run in pinotBroker log

Elon · Answer

Stack trace is basically that the post failed from controller Also server does not have any logs maybe request never makes it that far

Mayank · Answer

Is there an OOM

Elon · Answer

I don t see an oom or anything in the logs The main consumer of memory ran jmap was the async logger Also the table only has 4K rows When I lower the limit the query runs Then I raise it back and the query fails No crashes or ooms

Elon · Answer

Have you ever seen this I am retrying in local docker with debug logging on a test table though maybe I can find debug messages

Elon · Answer

Ok more debug info I see that it made it to the server

Elon · Answer

And broker parsed the query just before that about 10ms before

Elon · Answer

So it looks like something that happened after broker received the response from the server

Elon · Answer

Server completed the response ``` Processed requestId=2 table=alltypes REALTIME segments queried processed matched consuming =1 1 1 1 schedulerWaitMs=5 reqDeserMs=0 totalExecMs=4 resSerMs=0 totalTimeMs=12 minConsumingFreshnessMs=1625069569193 broker=Broker f068e4137900 8099 numDocsScanned=11 scanInFilter=0 scanPostFilter=176 sched=fcfs```

Jackie · Answer

I can reproduce the issue let me look further into it

Elon · Answer

Thanks

Elon · Answer

< Jackie> looks like it occurs after the `reduceOnDataTable` call in SingleConnectionBrokerRequestHandler processBrokerRequest

Elon · Answer

Should I create a github issue for it

Jackie · Answer

< Elon> Yes please create an issue and we can post the findings there

Elon · Answer

will do