This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
UseSuperReadOnly: applying super-read-only #390
Merged
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
added 6 commits
January 28, 2018 14:09
shlomi-noach
temporarily deployed
to
production/mysql_cluster=concertmaster
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #376
This PR supports
super_read_onlyas follows:UseSuperReadOnly, defaultsfalse.true,orchestratorwillset global super_read_only=?in addition to settingread_only.super_read_onlyonly exists in specific MySQL flavors and versions,orchestratorwill not bail out with error when unable toset global super_read_only=?. Instead, it will only log an error.orchestratormay also auto-detect whether a server supportssuper_read_only.