[Bug] BanyanDB data node OOMKilled by write trace data with secondary index #13528
Description
Search before asking
- I had searched in the issues 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.
Here is the heap dump result of data-node-0 before OOMKilled:
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
- I agree to follow this project's Code of Conduct