-
Notifications
You must be signed in to change notification settings - Fork 29
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
Enhance MySQLDown
alert
#2186
base: main
Are you sure you want to change the base?
Enhance MySQLDown
alert
#2186
Conversation
/cherry-pick stable/2024.1 |
@mnaser: once the present PR merges, I will cherry-pick it on top of stable/2024.1 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cherry-pick stable/2023.2 |
/cherry-pick stable/2023.1 |
@mnaser: once the present PR merges, I will cherry-pick it on top of stable/2023.2 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cherry-pick stable/zed |
@mnaser: once the present PR merges, I will cherry-pick it on top of stable/2023.1 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@mnaser: once the present PR merges, I will cherry-pick it on top of stable/zed in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Due to MySQLDown being very noisy even the mysql cluster still running above minimal replication, so we need to enhance it
this pr will replace the
MySQLDown
withMysqlClusterDown
,MysqlClusterDown
have two severity P3(warning) and P5(info). i.e when we have 5 percona-xtradb and only 1 replication down it only triggerMysqlClusterDown
with P5 because the mysql cluster still can operational normally but if we lost 3 replication(which means there only 2 replication) it will triggerMysqlClusterDown
with P3 since mysql cluster unable to operate