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

What happens when I set the replica to 2? #4461

Closed
lifeofmoo opened this issue Apr 16, 2024 · 2 comments
Closed

What happens when I set the replica to 2? #4461

lifeofmoo opened this issue Apr 16, 2024 · 2 comments

Comments

@lifeofmoo
Copy link

lifeofmoo commented Apr 16, 2024

Hello,

We've deployed kube-prometheus-stack chart and it's running great!

The main prom pod is a count of one (replicas: 1)

We've set the replica count to 2 in the helm chart. However we're unsure if this will cause adverse behavior.

What happens under the hood if we leave this at replica=2? Are we getting any HA benefits by doing so?

@jkroepke
Copy link
Member

If you run Prometheus with replica 2, both prometheus will scrape and save the data.

Since prometheus doesn't have a cluster capabilities, both instance runs on they own and does not know from each other.

For a Prometheus HA solution, you many need specialized solution like Thanos, Cortex or Mimir

@kfox1111
Copy link
Contributor

Its part of prometheus's ha design to run two prometheus instances, and an alertmanager cluster, and alertmanager will squash duplicate notifications when all is working properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants