-
Notifications
You must be signed in to change notification settings - Fork 462
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
Feature: Support HA setup for ClickHouse metrics exporter #1482
Comments
carlos4ndre
changed the title
Feature: Allow override endpoint that targets clickhouse-metrics-exporter
Feature: Support HA setup for clickhouse metrics exporter
Aug 11, 2024
carlos4ndre
changed the title
Feature: Support HA setup for clickhouse metrics exporter
Feature: Support HA setup for ClickHouse metrics exporter
Aug 11, 2024
The idea to extract metrics operator as a completely separate entity has been around for some time. However, tasks with higher priority are blocking this notion. We need to continue discussion and gather arguments pro and contra. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Assuming we want to run the ClickHouse metrics exporter with HA (Highly Availability), one would need to deploy it separately from the ClickHouse operator, which can only run with a single replica.
Currently, state is propagated from the ClickHouse operator to the ClickHouse metrics exporter running within the same pod, but in case the ClickHouse operator is down so will the metrics exporter service.
A possible solution would be to change/extend the ClickHouse metrics exporter logic to do polling or periodically check for updates reusing the logic in DiscoveryWatchedCHIs.
The text was updated successfully, but these errors were encountered: