Skip to content
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

Expose number of unreachable cluster peers via Prometheus (backport #9465) (backport #9473) #9474

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 19, 2023

This is an automatic backport of pull request #9473 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@michaelklishin michaelklishin added this to the 3.11.24 milestone Sep 19, 2023
@mergify mergify bot added the bazel label Sep 19, 2023
Unreachable peers is a subset of DB cluster nodes that are not connected
to the current node via Erlang distribution for any reason.

(cherry picked from commit e009a0a)
(cherry picked from commit 2b29976)
@michaelklishin michaelklishin force-pushed the mergify/bp/v3.11.x/pr-9473 branch from 5169d68 to 6b77950 Compare September 19, 2023 22:58
@michaelklishin michaelklishin removed this from the 3.11.24 milestone Sep 19, 2023
@michaelklishin michaelklishin deleted the mergify/bp/v3.11.x/pr-9473 branch September 19, 2023 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants