hanahmily opened a new issue, #13690: URL: https://github.com/apache/skywalking/issues/13690
### 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 There is a bug in BanyanDB’s trace module that can lead to disk space exhaustion when a merge operation fails. Two related issues have been observed: 1. The error handler does not clean up temporary files after a failed merge. 2. `trace` and `sidx` do not share the same view of memory parts, which can cause `sidx` merge failures. As a result, when merges fail, temporary files accumulate on disk without being removed, eventually exhausting available disk space. ### What you expected to happen • Temporary files created during the merge are not cleaned up after a failure. • `sidx` merges can fail due to inconsistent views of memory segments between `trace` and `sidx`. • Disk usage keeps increasing over time as more failed merges leave temporary files behind. ### How to reproduce 1. Trigger a trace merge operation (details to be filled in based on your environment/test setup). 2. Force or simulate a merge failure (e.g., by injecting an error, killing the process at a specific point, or using a faulty configuration). 3. Inspect the data directory used by the trace module. ### 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]
