We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, we have a node lock that has proven to work really well for 3+ node deployments.
However, as we scale below 3, the lock will eventually switch its backend from the opensearch index .charm-node-lock to the peer relation databag.
.charm-node-lock
This is really confusing, as the lock code itself gets filled with if/elif/else options to handle these cases.
if/elif/else
My proposal is to simplify this lock:
acquired
The text was updated successfully, but these errors were encountered:
https://warthogs.atlassian.net/browse/DPE-5125
Sorry, something went wrong.
phvalguima
No branches or pull requests
Currently, we have a node lock that has proven to work really well for 3+ node deployments.
However, as we scale below 3, the lock will eventually switch its backend from the opensearch index
.charm-node-lock
to the peer relation databag.This is really confusing, as the lock code itself gets filled with
if/elif/else
options to handle these cases.My proposal is to simplify this lock:
acquired
method.The text was updated successfully, but these errors were encountered: