Closed kostya9 closed 1 year ago
The code that counts max tag value bytes is not exact, but just attempts to cut off the returned tags roughly when the threshold is crossed. I would either lower max_bytes_per_tag_values_query
or raise the grpc message sizes:
server:
grpc_server_max_recv_msg_size: <some value in bytes>
grpc_server_max_send_msg_size: <some value in bytes>
I see, thanks. I can suggest adding this to docs - that ResourceExhausted grpc error in this case could be due to tags values exceeding a certain size.
When searching for span names, I encounter ResourceExhausted error.
In logs, this looks like this:
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect that tag values should be limited by config (e.g. we currently set it via
max_bytes_per_tag_values_query: 5000000
), so this error should not probably manifest itself.Environment:
Additional Context This error looks like it depends on the data we store somehow, however I still would expect it just to limit the values.
Config