Caused by: com.linecorp.armeria.common.ContentTooLargeException: maxContentLength: 10485760, contentLength: 16377153, transferred: 10491274

[fruitfish]

skywalking version : 9.5.0

when I query the trace with the condition "duration", reporting a mistake。
view log

Caused by: com.linecorp.armeria.common.ContentTooLargeException: maxContentLength: 10485760, contentLength: 16377153, transferred: 10491274

I set the config SW_STORAGE_ES_BATCH_OF_BYTES: 31457280（default value is 10485760).

[fruitfish]

question continue:
It is still reporting the mistake. Caused by: com.linecorp.armeria.common.ContentTooLargeException: maxContentLength: 10485760, contentLength: 16377153, transferred: 10491274
Searching the startup log, the config SW_STORAGE_ES_BATCH_OF_BYTES is 31457280.

How can I resolve this problem?
@chenhaipeng @wu-sheng
#10287
Thank you!

[chenhaipeng]

1. This problem seems to be a limitation of Armeria. The reason is that the return data of response is too large. See the default configuration: defaultMaxResponseLength

2. SW_STORAGE_ES_BATCH_OF_BYTES is to solve the problem of a single flush batch being too large during ES insertion. For example, if you insert >10M each time, ES may reject your request;

3. How to solve your problem? Query in kibana of ES to confirm whether your data return is too large. If so, it is recommended to streamline the reporting or temporarily adjust the limitations of the Armeria client.

[wu-sheng]

@chenhaipeng Although I think 10m is a reasonable length, do you ever face responses over 10m?

[chenhaipeng]

Not yet, 10M is also the default value of armeria defaultMaxRequestLength and defaultMaxResponseLength

[wu-sheng]

OK. I am not sure whether we should consider to expose this configuration?

[fruitfish]

I temporarily adjust the limitations of the Armeria client. It works! thank you very much!
And how can I streamline the reporting? Is the trace message too large? so When I query , the message returned is too large.
,