search

bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
9.01k stars 9.22k forks source link

[bitnami/influxdb] High-Availability Setup using influx 2.x #6813

Closed Anganthier closed 2 years ago

Anganthier commented 3 years ago

Which chart:

influxdb-2.2.6 App Version 2.0.6

Describe the bug

The influx-relay only distributes calls to /write to all servers. This is the api of influx v1 and exists only for backward compatibility.

Specifically a default bucket called primary is created on all replicas with different id's per replica. All statements which do write to the cluster using the V2 Api (create a bucket, create a user, create a org, ...) will only get written to one of the replicas

To Reproduce

Install a influx high-availabilty cluster with more than one replica

Expected behavior

A working cluster or a documented way how to set one up correctly for use with the V2 API.

Version of Helm and Kubernetes:

version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:10:43Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.10", GitCommit:"98d5dc5d36d34a7ee13368a7893dcb400ec4e566", GitTreeState:"clean", BuildDate:"2021-04-15T03:20:25Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}
alvneiayu commented 3 years ago

hi @Anganthier

I am not expert in InfluxDB. We are using the influxdb relay from influxdata. Could you help me to find some documentation to configure the InfluxDB like you are sharing with us, please? With this documentation, I will open an internal task to try to evaluate how to implement it in our solutions.

Thanks a lot

Álvaro

Anganthier commented 3 years ago

hi @alvneiayu ,

checking the influxdb-relay project it seems that they do not support 2.0 and probably never will. It is not maintained anymore.

https://github.com/influxdata/influxdb-relay/issues/81

So high-availabilty with influx 2.0 and influxdb-relay won't work in a stable way anymore.

bye David

alvneiayu commented 3 years ago

hi @Anganthier

I created an internal task to investigate about this problem and added it to the backlog. I am not able to give you an ETA. We will update this thread once we have news.

Thanks a lot for your time

Álvaro

marcosbc commented 2 years ago

From the concern in #9275, I'm going to push for the re-priorization of the internal task, as we are not able to support InfluxDB 1.x anymore. Unfortunately I'm unable to provide any ETA for when it could be done.

In the meantime, PRs are welcome! We would be glad to help with the review and release of those changes to push this feature forwards with 2.x.

carrodher commented 2 years ago

Unfortunately, this issue was created a long time ago and although there is an internal task to fix it, it was not prioritized as something to address in the short/mid term. It's not a technical reason but something related to the capacity since we're a small team.

Being said that, contributions via PRs are more than welcome in both repositories (containers and charts). Just in case you would like to contribute.

During this time, there are several releases of this asset and it's possible the issue has gone as part of other changes. If that's not the case and you are still experiencing this issue, please feel free to reopen it and we will re-evaluate it.