[tempo-distributed] added configuration option to set maxUnavailable for PDBs
#3104
Conversation
This file contains 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
Signed-off-by: Sy Babayev <s.babayev@mwam.com>
|
|
sy-be
requested review from
mapno,
swartz-k,
BitProcessor and
faustodavid
as code owners
sy-be
changed the title
maxUnavailable for PDBsmaxUnavailable for PDBs
sy-be
changed the title
maxUnavailable for PDBsmaxUnavailable for PDBs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
At the moment PDBs created as part of Tempo installation has their
maxUnavailablestatically set to 1 (except foringester). This PR makes this value configurable with defaults set as before.The change is backwards compatible as it has default values set to 1 and for the
ingesteris set to the template expression as before.