influxdata / influxdata/kapacitor

How to use 2 or more Influxdb's as a cluster and use them in Kapacitor

Open
#2,093 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

How to use 2 or more Influxdb's as a cluster and use them in Kapacitor?
Basically, we want to have HA setup for Influxdb with multiple instances.

To achieve this: In Telegraf, we have replicated the influxdb output section multiple times by referring multiple influxdb urls.
We kept HAProxy in front of Influxdb instances to load balance. we have used Loadbalancer VIP on Kapacitor config to communicate.

1. **How kapacitor will query the data from the above Influx cluster is it round robbin or FIFS or any logic behind it**.

2. **What is the best way to form an Influx cluster without using the Enterprise version for both read and writes?**

3. **How to identify from which Influx the alert has been triggered (any tag will be applied?)**

4. **In Influx cluster config we have to use one for write .. another one for Write. Is that the same case for the normal cluster(Open source version of Influx)**

5. **can we make a read or write specific cluster to accept both R+W when one of the cluster fails(like in case of Disaster recovery)**
_https://github.com/influxdata/kapacitor/issues/911_

please let me know if there are any best practices or guide to achieve the above scenarios.

Your help will be much appreciated!!

Contributor guide

Open the contributing guide

Research direction

Review the described Telegraf outputs, HAProxy VIP, and Kapacitor configuration alongside the linked issue #911. Verify how query routing, read/write failover, and alert provenance are documented for an open-source InfluxDB setup. Done means identifying a supported topology and documenting answers to the five deployment questions.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems, observability-sre
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.