Skip to content
This repository was archived by the owner on Apr 2, 2024. It is now read-only.
This repository was archived by the owner on Apr 2, 2024. It is now read-only.

flag provided but not defined: -high-availability #1073

@garlickim

Description

@garlickim

I upgraded promscale from 0.7.1 to 0.8 version.

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".

if i wasn't wrong, plz update the doc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions