docs(buffers): note known restart bugs in disk buffer docs

[pront]

Summary

Adds a brief callout to the buffering model docs noting the known disk buffer restart bugs, with a link to the open issue list.

Vector configuration

N/A

How did you test this PR?

Docs-only change.

Change Type

• Bug fix
• New feature
• Dependencies
• Non-functional (chore, refactoring, docs)

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

• Related: failed to seek to position where writer left off #25642, Uptick in dropped events from disk buffer InvalidProtobufPayload errors #18130, unable to be deserialized error on disk buffer block vector sending data out #18336, Hitting "failed to decode record immediately after encoding it" frequently #20212

[jonasrichard]

@pront If we want to give it a try and fix the issue, do you have any idea where and why the issue can come up.

About where I would go into lib/vector-buffers and see how they persistent 'pointers' are handled. But I have no idea the design of that, if it is support to implement some crash-safe solution.

Also do you know any minefield which I should be aware of?

[pront]

@pront If we want to give it a try and fix the issue, do you have any idea where and why the issue can come up.

About where I would go into lib/vector-buffers and see how they persistent 'pointers' are handled. But I have no idea the design of that, if it is support to implement some crash-safe solution.

Also do you know any minefield which I should be aware of?

Hi, @jonasrichard it depends on your pipeline, for example we observed bugs across Vector restarts. Generally, please take a look at the open issues and comment on those.

[janine-c]

Very small and optional style suggestion 🙂