FTDC opened a new issue, #9961: URL: https://github.com/apache/skywalking/issues/9961
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component OAP server (apache/skywalking) ### What happened when the log data is too large, the trace log can't recorded. because the elasticsearch keywork type max lenth is UTF8 encoding is longer than the max length 32766 sugguest keep a record and ignore any unnecessary information After setting ignore_above, data beyond the specified length is not indexed and cannot be returned through term exact matching retrieval https://www.elastic.co/guide/en/elasticsearch/reference/5.4/ignore-above.html#ignore-above%3E ### What you expected to happen trace log insert elastic error "caused_by": { "type": "illegal_argument_exception", "reason": "Document contains at least one immense term in field=\"content\" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[49, 53, 55, 56, 52, 54, 51, 51, 51, 118, 99, 111, 109, 115, 97, 100, 112, 97, 110, 100, 97, 117, 115, 115, 97, 102, 101, 114, 118, 112]...'" } ### How to reproduce GRPC-LOG record more than 32766 [whose UTF8 encoding is longer than the max length 32766] length word ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
