[FORWARD-PORT 4.0.z] Introduce NODE_AWARE partitioning group type #17913
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.
For Kubernetes based environments, user might want to store their backups at another Kubernetes node. They can easily decide which pod will be running on which node via defining affinity or node-selector. To satisfy these kind of specific requirements,
NODE_AWARE
partition group type is introduced with this PR. Newly createdNodeAwareMemberGroupFactory
class is just simplified version of ZoneAwareMemberGroupFactory actually. Here is the related PRD.(cherry-picked from commit 278db00)
forward-port of #17889