mrproliu opened a new issue, #13501: URL: https://github.com/apache/skywalking/issues/13501
### 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 When writing metric data to Banyandb during stree testing, I observed that the memory usage of one liaison node would continuously spike until it reached 100% utilization, at which point it was terminated by Kubernetes OOMKill. <img width="1655" height="613" alt="Image" src="https://github.com/user-attachments/assets/843deae6-83ae-432f-acb0-5dd7fa40ca9d"; /> <img width="1654" height="778" alt="Image" src="https://github.com/user-attachments/assets/219cd79e-12ef-4cc8-89f1-4616bd830910"; /> When the memory usage of the liaison node approached 80%, I profiled memory using pprof. Here is the memory flamegraph: <img width="1880" height="650" alt="Image" src="https://github.com/user-attachments/assets/7103853f-abc0-4aa7-a27e-1d2cbbf28da6"; /> ### What you expected to happen No OOMKill in the liaison node. ### How to reproduce 1. Deploy 2 liaison and 2 data nodes in Kubernetes. 2. Keep write metrics. ### 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]
