I am setting up high availability influxdb setup as mentioned on influxdb site.
loadbalancer-->relay-->influxdbs(pri/sec) and kapacitor Though there are obvious advantages to sending real time traffic via influxdbrelay to Kapacitor together with influxdbs,it takes away flexibility to spin up multiple kapacitors in the environment without updating relay configuration. Our usecase has several teams who want to control their own alerting configuration in kapacitor so we are looking for spinning up multiple kapacitors in the environment (one controlled by each team). I have couple questions around that: 1) Do you forsee any issues with having multiple kapacitors in the environment talking to same influxdb servers (if they subscribe themselves to influxdb servers instead of relay pushing traffic to kapacitors for which it would need to be updated). 2) If i have two influxdb servers which are identical (primary and secondary), where should my kapacitor point to? (load balancer DNS or influxdb-primary and influxdb-secondary in the list [host1, host2]? 3) How many tasks can one kapacitor handle ( I can throw as many resources (cpu/ram) on it as i want)? Thanks Kirtimaan -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/9bd7dc3b-9097-4a43-8df5-fadb2738de5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
