hanahmily commented on issue #13862: URL: https://github.com/apache/skywalking/issues/13862#issuecomment-4435963850
Hi @Felix-wave, The fix for this merge durability gap has been backported to the `v0.10.x` branch ([`fix(banyand): close merge durability gap (#13862) (#1118)`](https://github.com/apache/skywalking-banyandb/commit/af88eb86)). Together with the fix for trace `block_writer` panic on out-of-order timestamps within the same traceID ([#1114](https://github.com/apache/skywalking-banyandb/commit/468cb5d4)), these two patches address the torn-part and CrashLoopBackOff issue you reported in #13861. Would you be willing to test your workload against the `v0.10.x` branch before we cut the `0.10.3` release? That would help us confirm the fix is effective in your environment. BanyanDB doesn't publish nightly images for non-main branches, so you'll need to build from source. You can follow the [build instructions](https://github.com/apache/skywalking-banyandb/blob/main/docs/en/setup/banyandb-server/docker-setup.md) to build the Docker image from the `v0.10.x` branch. If you run into any issues building the images, feel free to ask me for help. As noted in the issue, pre-existing torn parts on disk will still trigger the panic-at-boot (BanyanDB's canonical fail-fast signal) — those need to be moved aside manually. After that, the fix prevents new torn parts from being created. -- 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]
