This message was deleted.
# troubleshootings
Slackbot
09/12/2022, 5:10 PMThis message was deleted.
g
Gian Merlino
09/13/2022, 12:42 AMwith a large resultset like that, you could be hitting timeouts leading to truncation of results
Gian Merlino
09/13/2022, 12:42 AMsee this section of the docs for info on errors in the SQL API: https://druid.apache.org/docs/latest/querying/sql-api.html#errors
Gian Merlino
09/13/2022, 12:43 AMthis part:
As a caller, it is important that you properly handle response truncation. This is easy for the object and array formats, since truncated responses will be invalid JSON. For the line-oriented formats, you should check the trailer they all include: one blank line at the end of the result set. If you detect a truncated response, either through a JSON parsing error or through a missing trailing newline, you should assume the response was not fully delivered due to an error.
Gian Merlino
09/13/2022, 12:44 AMwith CSV, a complete API response always includes a trailing blank line — if you don't see that then it means the response got cut off due to error/timeout. you can increase your timeout in that case
s
Sourav Saraf
09/13/2022, 9:19 AMWhat and where are those config which I can change to get the whole query response instead of truncated response @Gian Merlino?
I could not find much from the documentation actually..
g
Gian Merlino
09/13/2022, 4:39 PMi'm just guessing it's timeout-related, which is described here under property
timeouts
Sourav Saraf
09/14/2022, 2:25 PMOhh. unfortunately that does not work when I pass the
timeoutSourav Saraf
09/15/2022, 2:23 PMEven using timeout of 0 we are getting below error -
Copy code
AvaticaClientRuntimeException: Remote driver error: QueryTimeoutException: url[<http://10.111.125.60:8083/druid/v2/>] timed out. Error -1 (00000) UNKNOWN
org.apache.druid.query.QueryTimeoutException: url[<http://10.XXX.XXX.XX:8083/druid/v2/>] timed out
at org.apache.druid.client.JsonParserIterator.timeoutQuery(JsonParserIterator.java:204)
at org.apache.druid.client.JsonParserIterator.next(JsonParserIterator.java:119)
at org.apache.druid.java.util.common.guava.BaseSequence.makeYielder(BaseSequence.java:90)
at org.apache.druid.java.util.common.guava.BaseSequence.access$000(BaseSequence.java:27)
at org.apache.druid.java.util.common.guava.BaseSequence$1.next(BaseSequence.java:114)
at org.apache.druid.java.util.common.guava.MergeSequence.makeYielder(MergeSequence.java:1Sourav Saraf
09/15/2022, 2:24 PMI have infact increased the timeout on broker, historical, MM to 20 mins. Still failing.. 😞
g
Gian Merlino
09/15/2022, 8:12 PMhmm. about how long is it failing after?
Gian Merlino
09/15/2022, 8:15 PMi wonder if you are running into one of the other things mentioned on https://druid.apache.org/docs/latest/configuration/index.html such as
druid.broker.http.readTimeoutdruid.router.http.readTimeouts
Sourav Saraf
09/19/2022, 7:06 AMIts failing approx after 5 mins of
g
Gian Merlino
09/19/2022, 5:20 PMYeah that does sound like a timeout thing! Try setting longer timeout in query context, like, if 15 mins is OK then set
timeout: 900000druid.router.http.readTimeout = PT15M2 Views