Add validation for unique volume IDs in JBOD storage #9990
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.
Type of change
Description
Currently, we do not seem to have any validation that all JBOD storage IDs are unique. And when we have duplicate, we end-up breaking the first pod because we generate invalid Pod definition:
This PR adds the validation of duplicate volume IDs to the
StorageDiff
class. That allows us to proceed with reconciliation using the old storage definition. This Pr also refactors the previously added check for multiple KRaft metadata volumes to reduce the cyclomatic complexity and adds a debug log message indicating what the actual problem is to both checks.Checklist