FrankChen021 commented on a change in pull request #11333:
URL: https://github.com/apache/druid/pull/11333#discussion_r646246239
##########
File path: docs/querying/querying.md
##########
@@ -144,5 +144,5 @@ Possible Druid error codes for the `error` field include:
|`Query timeout`|504|The query timed out.|
|`Query interrupted`|500|The query was interrupted, possibly due to JVM
shutdown.|
|`Query cancelled`|500|The query was cancelled through the query cancellation
API.|
-|`Truncated response context`|500|An intermediate response context for the
query exceeded the built-in limit of 7KB.<br/><br/>The response context is an
internal data structure that Druid servers use to share out-of-band information
when sending query results to each other. It is serialized in an HTTP header
with a maximum length of 7KB. This error occurs when an intermediate response
context sent from a data server (like a Historical) to the Broker exceeds this
limit.<br/><br/>The response context is used for a variety of purposes, but the
one most likely to generate a large context is sharing details about segments
that move during a query. That means this error can potentially indicate that a
very large number of segments moved in between the time a Broker issued a query
and the time it was processed on Historicals. This should rarely, if ever,
occur during normal operation.|
Review comment:
According to the code, its `7KiB`
https://github.com/apache/druid/blob/0c5d1c9725303111df69198a232166ddf00672d2/server/src/main/java/org/apache/druid/server/ResponseContextConfig.java#L29
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
