Add two prometheus replicas for high availability #71
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
flightdeck-prometheus is used for autoscaling as well, so if this goes down for whatever reason or whatever node, then it would cause the site to suffer performance problems. We can mitigate this risk by having multiple nodes. This also means currently our federated instance is getting twice as much data, since it's pulling from both replicas and not being deduplicated yet.
ayellapragada
force-pushed
the
ay-add-replicas
branch
from
4ed1916 to
34c8a52
Compare
jferris
approved these changes
Nov 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
flightdeck-prometheus is used for autoscaling as well, so if this goes
down for whatever reason or whatever node, then it would cause the site
to suffer performance problems. We can mitigate this risk by having
multiple nodes.
This also means currently our federated instance is getting twice as
much data, since it's pulling from both replicas and not being
deduplicated yet.