This repository has been archived by the owner on Jan 20, 2025. It is now read-only.
Consul: allow clustering with nodes in warning status #10
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.
moved from aweber#140
Consul agent may be configured with additional health checks, besides the TTL one created by the plugin. Some of these checks may expect a converged cluster. If any of those additional checks is not passing the corresponding nodes will be excluded from the list for clustering which is not always the desired situation.
This change aims to provide flexibility to define additional health checks while avoiding interference with auto clustering. This is consistent with Consul's
only-passing
option which determines whether nodes with warning status are excluded from the DNS response.