Peer discovery: disable consul health check helper when registration is disabled (backport #13210) #13213
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.
Proposed Changes
This is a follow-up PR for #13201. In that PR a new configuration option was added:
cluster_formation.registration.enabled
.For Consul, this does work during boot, but the
rabbitmq_peer_discovery_consul_health_check_helper
keep querying Consul periodically to see whether the node is healthy. If it is not, it will register the node even though the registration was disabled. Since the periodic health check has no other function than to register the node if unhealthy, the periodic check needs to be disabled when registration is disabled.I have tested this PR with Consul and Nomad.
Types of Changes
Checklist
CONTRIBUTING.md
documentThis is an automatic backport of pull request Peer discovery: disable consul health check helper when registration is disabled #13210 done by Mergify.