Do not produce a HA policy config when $ha_policy is unset #6
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
Doing so will create a clustered server using the default HA policy which is a "live only" configuration.
fraenki
approved these changes
Aug 2, 2023
|
Merged, thanks! |
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.
Doing so will create a clustered server using the default HA policy which is a "live only" cluster configuration which does not feature replication of persistent data.
This resolves part of issue #4.
When ha_policy is
undefno<ha-policy>entry is created, when it is set tolive-onlyit will produce<ha-policy><live-only></live-only></ha-policy>. Both result in the same effective configuration.There is no support for configuring the scale-down