Use InfluxDB default [http]/max-row-limit setting
Since version 1.2.2, InfluxDB uses 0 (unlimited) as default value for [http]/max-row-limit [1]. Using the default value resolves an issue with the CloudKitty v1 API returning only 10000 dataframes. [1] https://docs.influxdata.com/influxdb/v1.7/about_the_project/releasenotes-changelog/#v1-2-2-2017-03-14 Change-Id: I6eb8c1216e3a9295b7d8cb7fbcbb8778ae7caf7e Closes-Bug: #1862358
This commit is contained in:
parent
c5b4ca4f1f
commit
fc3492bcb1
@ -42,7 +42,6 @@ reporting-disabled = true
|
||||
write-tracing = false
|
||||
pprof-enabled = false
|
||||
https-enabled = false
|
||||
max-row-limit = 10000
|
||||
[[graphite]]
|
||||
enabled = false
|
||||
[[opentsdb]]
|
||||
|
@ -0,0 +1,8 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Removes the ``[http]/max-row-limit = 10000`` setting from the default
|
||||
InfluxDB configuration, which resulted in the CloudKitty v1 API returning
|
||||
only 10000 dataframes when using InfluxDB as a storage backend. See `bug
|
||||
1862358 <https://bugs.launchpad.net/kolla-ansible/+bug/1862358>`__ for
|
||||
details.
|
Loading…
x
Reference in New Issue
Block a user