mrproliu opened a new issue, #13528: URL: https://github.com/apache/skywalking/issues/13528
### 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 BanyanDB (apache/skywalking-banyandb) ### What happened I have created a new BanyanDB cluster with a trace-related index, and I continue to write trace data with small traffic (50 spans per streaming, sleeping for 300 milliseconds per streaming). Seems the BanyanDB data node will OOM-kill. The screenshots below show that the data-node-0 has been OOMKilled at 12:04. Then I have stopped the traffic, and the memory of data-node-1 has been reduced to normal at 12:06. <img width="1643" height="635" alt="Image" src="https://github.com/user-attachments/assets/12a9532c-f065-48f0-8886-32c788288e5a"; /> <img width="1654" height="564" alt="Image" src="https://github.com/user-attachments/assets/4852c4ae-ca01-442a-b23a-6ed27d84b64f"; /> Here is the heap dump result of data-node-0 before OOMKilled: [heap-data-node-0.zip](https://github.com/user-attachments/files/22588930/heap-data-node-0.zip) ### What you expected to happen No OOMKill in the data node. ### How to reproduce Keep writing trace data into the BanyanDB cluster. ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### 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]
