Add procedure to set cluster to read-only #724
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
Signed-off-by: Masayuki Ishii <[email protected]>
ymmt2005
reviewed
Aug 5, 2024
docs/usage.md
Outdated
| You can check whether the cluster is read-only with the following command. | ||
|
|
||
| ```console | ||
| $ kubectl moco mysql -it <CLSUTER_NAME> -- -e "SHOW GLOBAL VARIABLES like 'super_read_only'" |
There was a problem hiding this comment.
nit. I usually use SELECT @@super_read_only;.
There was a problem hiding this comment.
Thank you. I updated. ce6332b
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.
This PR adds a procedure to set MySQL clusters to read-only.
If an user simply sets the "(super_)read_only" variable, MOCO will remove it in the clustering process.
And it can lead to accidents.
Therefore, I specify the procedure to stop clustering and make the cluster read-only.