Couchbase Server Replacement Automation #27
Conversation
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
* master: Changed the user and group for /fulla to ec2-user Changed cluster to group in the code sample Checked for existing log handlers before adding a new one Fixed the comparison of IAM policies.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Like the
replace_mongo_serverfunction, this automates the replacement of a single member in a cluster.A new Couchbase server will be spun up, added to the Couchbase cluster. If
replaceisTrue, the old server will be removed from the cluster. IfrerouteisTruethen before the old server is removed, the DNS record for the old server will be changed to point to the new server, which means that clients don't need to be immediately updated. In addition, the old server will not be removed until the updated DNS record has "propagated." If the server is being replaced, it will also be stopped, or optionally terminated. Either way, it will be placed in Maintenance Mode on Stackdriver first.