-
Notifications
You must be signed in to change notification settings - Fork 17
[DPE-8050] Backup action cluster checks #679
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
Conversation
f26cb28
to
a653ea0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a653ea0
to
24a435e
Compare
PR branch rebased from |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, but please include extra text in action and update documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, please indicate it properly in the official documentation and the next release notes. It is an important changes.
P.S. please check Mykola comments before merging.
eab3ebc
to
9b0f7c6
Compare
9b0f7c6
to
68a3e21
Compare
This PR adds a cluster health check to the
create-backup
action, which can be overridden using theforce
param.The MySQL cluster could be in any of the states listed in this documentation page. From those, only
OK
andOK_PARTIAL
are considered safe, given that the rest of the states could introduce downtime (like the no-tolerance states) or data-loss (lost quorum, error, etc), when performing a backup.Additional changes
PropertyMock
class has been simplified.