zil: add stats for commit failure/fallback #16315
Merged
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.
[Sponsors: Klara, Inc., Wasabi Technology, Inc.]
Motivation and Context
There's no good way to tell when a ZIL commit fails and falls back to a transaction sync, other than perhaps a throughput drop. This adds counters so we can see when it happens and why.
Description
Adds three new counters to the
zil
kstat for each of the three places where a ZIL commit can fail and fall back to a full sync. From the comments:error
: ZIL IO (write/flush) returned an error (seezil_commit_impl()
)stall
: LWB block allocation failed, ZIL chain abandoned (seezil_commit_writer_stall()
)suspend
: Commit was requested but ZIL suspended (seezil_commit()
)How Has This Been Tested?
Manual. These stats are also used to implement a test case for a PR to change flush behaviour that I'm about to post.
Full ZTS run completed successfully.
Types of changes
Checklist:
Signed-off-by
.