New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitor 'Group replication' rework #4082
Merged
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
This is a draft of a rework for Monitor 'Group Replication', this reworks reuses the Monitoring model already taken for AWS Aurora for 'Group Replication'.
JavierJF
force-pushed
the
v2.x-group_replication_rework
branch
from
January 16, 2023 14:15
6711277
to
51c723f
Compare
When writer was set as SHUNNED due to replication lag, and 'mysql_servers' table was regenerated (via servers reconfiguration or other action). SHUNNED writer wasn't considered a found writer, triggering an unwanted server reconfiguration.
retest this please |
1 similar comment
retest this please |
…writers' Since servers present in 'backup_writer_hostgroup' where not considered as previously configured writers, everytime the number of available writers exceeded 'max_writers' an unwanted server reconfiguration was triggered for each of these servers at every monitoring action.
@JavierJF : I took the freedom to resolve the conflict. I hope it makes sense |
JavierJF
force-pushed
the
v2.x-group_replication_rework
branch
from
January 30, 2023 09:32
dfb4a5a
to
e98d028
Compare
JavierJF
force-pushed
the
v2.x-group_replication_rework
branch
from
January 30, 2023 11:06
e98d028
to
1188b0e
Compare
retest this please |
JavierJF
changed the title
DRAFT: Monitor 'Group replication' rework
Monitor 'Group replication' rework
Jan 30, 2023
retest this please |
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 is a rework for Monitor 'Group Replication', this reworks reuses the Monitoring model already taken for AWS Aurora for 'Group Replication'.
It also:
sys.gr_member_routing_candidate_status
.