-
Notifications
You must be signed in to change notification settings - Fork 523
Remove the cluster client #339
Comments
Hi, we are still using InfluxDB 0.11 with cluster, and that feature of influxdb-python was useful to us :( |
Yes, that.
okay.
|
Fine, thanks for taking time to explain the removal. I've created a PR (#396) to re-add the cluster in a legacy module with warning that state this cluster client must NOT be used with newer influxdb-relay cluster. |
We are using the latest commercial version of InfluxDB (v1.2 Enterprise) which does not rely on a relay server. This means the load balancing still needs to be done on the client, hence there is still a strong use case for the ClusterClient. The removal of this functionality means that we cannot upgrade to the latest release of influxdb-python. Are there any plans to support Influx-Enterprise? |
PR #396 should works with latest InfluxDB enterprise cluster, it only require that all nodes are equivalent: writing on one node is replicated by the node to the other nodes; reading from any node return the same data But since the ClusterClient is still useful in Influxdb enterprise, maybe the PR should not move it to a "legacy" module, but not normal module and/or "enterprise" module (e.g. with due warning that it does not works with relay cluster). What do you think @aviau, should I update the PR in this way ? |
The cluster client no longer makes sense with recent patches.
Don't forget:
The text was updated successfully, but these errors were encountered: