feat: introduce the Noop WAL provider for datanode #7105
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.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
close #7100
What's changed and what's your intention?
This PR introduces a Noop WAL provider for the datanode. It is designed for situations where the configured WAL provider becomes temporarily unavailable.
In a GreptimeDB cluster, there are two places where the WAL provider should be configured:
This means that when the WAL provider is temporarily unavailable, users only need to configure the datanode’s WAL provider as Noop to keep the cluster functional.
PR Checklist
Please convert it to a draft if some of the following conditions are not met.