enhancement(buffers): improve disk buffer lifecycle visibility - #26050
Draft
Jansen-w wants to merge 14 commits into
Draft
enhancement(buffers): improve disk buffer lifecycle visibility#26050Jansen-w wants to merge 14 commits into
Jansen-w wants to merge 14 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
orphaned_buffer_id.Vector configuration
No standalone configuration is required. The behavior applies to sinks configured with
buffer.type: diskduring startup and configuration reload.How did you test this PR?
cargo test -p vector --lib config::validation::testscargo test -p vector --lib topology::running::disk_buffer_drain_testscargo test -p vector --lib topology::test::reloadcargo test -p vector-buffers initial_size_correct_with_multieventscargo clippy -p vector -p vector-buffers --lib -- -D warningscargo vdev check changelog-fragmentsIs this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
None.