You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 2, 2024. It is now read-only.
it occured "flag provided but not defined: -high-availability" error..
The document(docs/high-availability/prometheus-HA.md) say
After Prometheus instances are configured to send the correct labels, Promscale simply needs to be started with the -high-availability CLI flag. Internally, Promscale will elect a single replica per cluster to be the current leader. Only data sent from that replica will be ingested. If that leader-replica stops sending data, then a new replica will be elected as the leader.
But I saw the history of code. I found changes.
If I use v0.8 of promscale, I have to change command from "-high-availability" to "-metrics.high-availability".