Implementation of ZoneawareEnsemblePlacementPolicy#2113
Merged
reddycharan merged 1 commit intoapache:masterfrom Jun 25, 2019
Merged
Conversation
- This is meant to be used in public cloud infrastructure in which Availability zones (AZs) are isolated locations within data center regions from which public cloud services originate and operate. - ZoneawareEnsemblePlacementPolicy is a placement policy implementation which uses zone information for placing ensembles. - In this PlacementPolicy, it is assumed the networktopology/networklocation is going to be two level tree, where first part indicates zoneid and the second part indicates upgradedomainid. - Here upgrade domain is a set of bookies in an AZ that can be brought down together for short term maintenance with no impact to the service. This would help in enabling parallel patching. - Upgrade domain is a logic concept/division and it may be mapped to cloud provider native cluster/grouping like Placement Groups in AWS. Introduce soft PlacementPolicyAdherence - for ZoneawarePlacementPolicy if in a writeset the number of zones are in between minnumofzones and desirednumofzones then it is considered MEETS_SOFT. - if all of the writesets have zones >= desirednumofzones then it is considered MEETS_STRICT - if a writeset contains < minnumofzones then it is considered FAIL - add corresponding metric for PlacementPolicyAdherence.MEETS_SOFT
Contributor
Author
|
requesting review. |
sijie
approved these changes
Jun 25, 2019
Contributor
|
Sorry. |
eolivelli
approved these changes
Jun 25, 2019
Contributor
eolivelli
left a comment
eolivelli
left a comment
There was a problem hiding this comment.
It's a great work.
The diff is huge, I did not find issues.
+1
Contributor
Author
|
Thanks @sijie @eolivelli @jvrao for the review. Since all checks have passed, I'm merging this PR. |
Contributor
|
@reddycharan hi, i am researching for how to use |
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
5 participants
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.
Descriptions of the changes in this PR:
Implementation of ZoneawareEnsemblePlacementPolicy
Availability zones (AZs) are isolated locations within data center
regions from which public cloud services originate and operate.
which uses zone information for placing ensembles.
is going to be two level tree, where first part indicates zoneid
and the second part indicates upgradedomainid.
down together for short term maintenance with no impact to the service.
This would help in enabling parallel patching.
cloud provider native cluster/grouping like Placement Groups in AWS.
Introduce soft PlacementPolicyAdherence
of zones are in between minnumofzones and desirednumofzones
then it is considered MEETS_SOFT.
then it is considered MEETS_STRICT
FAIL