# InfluxDB Tuning

**URL:** <https://community.influxdata.com/t/influxdb-tuning/1017>\
**Category:** Store\
**Created:** [May 22, 2017, 4:44pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017 "2017-05-22T16:44:03Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [May 22, 2017, 4:44pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/1 "2017-05-22T16:44:04Z")

</div>

Hi

Do we have any published tuning settings for InfluxDB community edition? i am hitting scaleing limits very often and wondering how much data or series InfluxDB can handle with decent config. i’m running InfluxDB in a container platform and increased memory from 2 GB to 30 GB now. I have just 120+ nodes collecting just basic standard input plug-ins + Docker metrics. i reduced retention policy also just 1 week since InfluxDB unable to handle memory properly.

Not sure what else need to be configured? I hit series limitation of 1M today. I increased series using max-series-per-database parameter Not sure why am hitting memory, series limitations although I just configured retention policy for just 1 week. i am assuming after one week, data will be dropped off. Whatever memory I put, it is eating with in few days. I am confusing what is the right configuration and how to handle future growth ?

my current configuration

]$ cat influxdb.conf  
[admin]  
enabled = true  
bind-address = “:8083”

[http]  
enabled = true  
bind-address = “:8086”  
auth-enabled = true

[coordinator]  
write-timeout = “30s”

[retention]  
enabled = true  
check-interval = “30m”

[monitor]  
store-enabled = true  
store-database = “\_internal”  
store-interval = “30s”

[meta]  
dir = “/var/lib/influxdb/meta”

[data]  
dir = “/var/lib/influxdb/data”  
engine = “tsm1”  
wal-dir = “/var/lib/influxdb/wal”  
max-series-per-database = 10000000

my telegraf is configured to collect metrics every 60 seconds. Dont worry about {{ }} varaibales as they automatically populated using ansible template language.

[global\_tags]  
cluster = “{{ cluster\_name }}”  
hostname = “{{ ansible\_nodename }}”  
datacenter = “{{ datacenter }}”

[agent]  
interval = “60s”  
round\_interval = true  
metric\_batch\_size = 1000  
metric\_buffer\_limit = 10000  
collection\_jitter = “5s”  
flush\_interval = “10s”  
flush\_jitter = “5s”  
precision = “”  
debug = false  
quiet = false  
logfile = “”  
hostname = “”  
omit\_hostname = true

[[outputs.influxdb]]  
urls = [“http://{{ rtp\_db\_ingress\_ip }}:{{ port }}”]  
database = “hosting”  
write\_consistency = “any”  
timeout = “30s”  
username = “hosting”  
password = “\*\*\*\*\*\*”  
user\_agent = “telegraf”  
udp\_payload = 512

[[outputs.influxdb]]  
urls = [“http://{{ rcdn\_db\_ingress\_ip }}:{{ port }}”]  
database = “hosting”  
write\_consistency = “any”  
timeout = “30s”  
username = “hosting”  
password = “\*\*\*\*\*\*\*\*”  
user\_agent = “telegraf”  
udp\_payload = 512

[[inputs.cpu]]  
percpu = true  
totalcpu = true  
collect\_cpu\_time = false

[[inputs.disk]]  
ignore\_fs = [“tmpfs”, “devtmpfs”]

[[inputs.diskio]]

[[inputs.kernel]]

[[inputs.mem]]

[[inputs.processes]]

[[inputs.swap]]

[[inputs.system]]

[[[inputs.net](http://inputs.net)]]

[[inputs.netstat]]

[[inputs.docker]]  
endpoint = “unix:///var/run/docker.sock”  
timeout = “30s”  
perdevice = true  
total = true  
docker\_label\_exclude = [“\*”]

[[inputs.procstat]]  
exe = “dockerd-current”  
prefix = “docker”

[[inputs.procstat]]  
exe = “openshift”  
prefix = “openshift”

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [May 23, 2017, 5:36pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/2 "2017-05-23T17:36:01Z")

</div>

I didn’t reply unfortunately. new upcoming 1.3 release wills solve some of memory issues? it seems no of series has direct impact on memory usage but even using 7 days retention policy how series are increasing and not stable always since no of nodes and measurements are same?

---

<div class="post-metadata">

**Author:** ![jason](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jason/32/1651_2.png) [@jason](https://community.influxdata.com/u/jason)\
**Post date:** [May 23, 2017, 7:48pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/3 "2017-05-23T19:48:53Z")

</div>

The number of series you have is your series cardinality. Every time you write a distinct measurement + tag set + field name, a new series is created. There is an in-memory index of all series stored in all shards. If you are continuously adding new series, your memory usage will continue to grow. Since you hit the `max-series-per-database` limit, that is an indication you may have a schema design/cardinality issue with the way you are storing data. I would take a look at the series you are writing and see if you are writing any tags that continuously changes. For example, writing a GUID, timestamp, or other highly variable tag values is a frequent cause of high cardinality data. You can also run `influx_inspect report -detailed /path/to/shard/data` to see if any particular tag or measurement stands out as having higher cardinality.

The retention policy defines how long data persist on disk. Once a shard has expired, it is marked for deletion and eventually removed. Any series that existed only in those expired shards are removed from the in-memory index at this time as well.

In your telegraf config, you may need to adjust the `procstat` plugin to drop tags that create high cardinality issues. I’m not sure what the default behavior is currently, there was this [bug](https://github.com/influxdata/telegraf/issues/1460) which recorded `pid` as a tag. That can lead to cardinality issues.

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [May 24, 2017, 3:17am UTC](https://community.influxdata.com/t/influxdb-tuning/1017/4 "2017-05-24T03:17:52Z")

</div>

Thanks you Jason. This info is really helpful, however the problem is how to find bottlenecks and tune them. As per documentation i knew there is issue with mutliple series and cardinality, but not much info is available, what tools or commands to use to find bottlenecks and fix them

The command you give me is really helpful to find the series cardinality and identify which input plug-in is causing more. since i have one week retention policy , i have multiple shards

ls -l /var/lib/influxdb/data/hosting/one\_week/  
total 32  
drwxr-xr-x. 2 root root 4096 May 18 07:38 222  
drwxr-xr-x. 2 root root 4096 May 19 04:59 230  
drwxr-xr-x. 2 root root 4096 May 20 04:13 238  
drwxr-xr-x. 2 root root 4096 May 21 04:13 246  
drwxr-xr-x. 2 root root 4096 May 22 04:13 254  
drwxr-xr-x. 2 root root 4096 May 23 05:24 262  
drwxr-xr-x. 2 root root 4096 May 24 00:10 270  
drwxr-xr-x. 2 root root 4096 May 24 03:12 279

I ran the commands against few shards and below is output

* * *

influx\_inspect report -detailed /var/lib/influxdb/data/hosting/one\_week/222/  
File Series Load Time  
000000772-000000004.tsm 741128 289.931213ms  
000000772-000000005.tsm 182434 57.268557ms

Statistics  
Series:  
Total (est): 923184  
Measurements (est):  
cpu: 19660 (2%)  
disk: 6141 (0%)  
docker: 1156 (0%)  
docker\_container\_mem: 196687 (21%)  
kubernetes\_node: 36 (0%)  
kubernetes\_pod\_container: 143 (0%)  
kubernetes\_pod\_volume: 21 (0%)  
docker\_container\_blkio: 318879 (34%)  
mem: 1050 (0%)  
procstat: 19349 (2%)  
swap: 630 (0%)  
kubernetes\_system\_container: 44 (0%)  
net: 27939 (3%)  
processes: 944 (0%)  
system: 735 (0%)  
diskio: 39392 (4%)  
docker\_container\_cpu: 291305 (31%)  
docker\_data: 315 (0%)  
docker\_metadata: 315 (0%)  
kernel: 419 (0%)  
kubernetes\_pod\_network: 48 (0%)  
netstat: 1362 (0%)  
Fields (est):  
kubernetes\_pod\_volume: 3  
kubernetes\_system\_container: 11  
mem: 10  
processes: 9  
kubernetes\_node: 18  
kubernetes\_pod\_container: 13  
docker\_container\_mem: 35  
net: 115  
procstat: 53  
system: 7  
cpu: 10  
docker: 13  
docker\_container\_cpu: 9  
docker\_metadata: 3  
netstat: 13  
swap: 6  
diskio: 110  
docker\_container\_blkio: 11  
kernel: 4  
kubernetes\_pod\_network: 4  
disk: 7  
docker\_data: 3  
Tags (est):  
unit: 1  
Vendor: 2  
release: 13  
version: 13  
com.redhat.dev-mode.port: 1  
io.kubernetes.container.name: 532  
io.kubernetes.container.restartCount: 1242  
com.redhat.dev-mode: 1  
com.docker.compose.version: 1  
process\_name: 542  
container\_image: 375  
io.kubernetes.container.terminationMessagePath: 1  
volume\_name: 3  
io.openshift.s2i.scripts-url: 2  
exe: 2  
datacenter: 3  
authoritative-source-url: 1  
com.redhat.component: 12  
container\_name: 5952  
distribution-scope: 1  
vendor: 2  
io.openshift.expose-services: 3  
Name: 11  
Version: 11  
container\_version: 539  
io.kubernetes.pod.terminationGracePeriod: 4  
io.kubernetes.pod.uid: 2217  
cpu: 183  
com.redhat.build-host: 11  
io.k8s.description: 14  
namespace: 5  
fstype: 2  
engine\_host: 388  
node\_name: 2  
interface: 1890  
com.docker.compose.service: 4  
name: 457  
Architecture: 1  
PostgresVersion: 2  
license: 1  
com.docker.compose.container-number: 1  
hostname: 457  
device: 536  
architecture: 1  
vcs-ref: 18  
com.docker.compose.oneoff: 1  
Build\_Host: 2  
io.kubernetes.pod.namespace: 273  
com.redhat.deployments-dir: 1  
io.openshift.tags: 13  
build-date: 35  
io.kubernetes.container.ports: 152  
com.docker.compose.config-hash: 4  
cluster: 3  
description: 2  
summary: 2  
io.openshift.builder-version: 1  
com.docker.compose.project: 1  
pod\_name: 12  
path: 7  
Authoritative\_Registry: 1  
vcs-type: 1  
BZComponent: 11  
Component: 1  
Release: 12  
io.kubernetes.container.hash: 1230  
io.k8s.display-name: 15  
io.kubernetes.pod.name: 2033  
Completed in 20.936049294s

=================

influx\_inspect report -detailed /var/lib/influxdb/data/hosting/one\_week/230/  
File Series Load Time  
000000653-000000005.tsm 847282 345.675756ms  
000000653-000000006.tsm 267516 95.470656ms

Statistics  
Series:  
Total (est): 1097999  
Measurements (est):  
kubernetes\_pod\_volume: 21 (0%)  
netstat: 1388 (0%)  
swap: 642 (0%)  
disk: 7279 (0%)  
docker\_container\_cpu: 355845 (32%)  
docker\_container\_mem: 238933 (21%)  
kernel: 427 (0%)  
mem: 1070 (0%)  
diskio: 41045 (3%)  
kubernetes\_pod\_container: 143 (0%)  
kubernetes\_pod\_network: 48 (0%)  
net: 28707 (2%)  
kubernetes\_node: 36 (0%)  
kubernetes\_system\_container: 44 (0%)  
processes: 1035 (0%)  
cpu: 21049 (1%)  
docker: 1178 (0%)  
docker\_container\_blkio: 397246 (36%)  
docker\_data: 321 (0%)  
docker\_metadata: 321 (0%)  
procstat: 5284 (0%)  
system: 749 (0%)  
Fields (est):  
docker\_container\_cpu: 9  
docker\_metadata: 3  
kubernetes\_pod\_container: 13  
kubernetes\_pod\_volume: 3  
netstat: 13  
system: 7  
cpu: 10  
docker: 13  
diskio: 114  
kubernetes\_system\_container: 11  
kernel: 4  
kubernetes\_node: 18  
kubernetes\_pod\_network: 4  
mem: 10  
net: 115  
swap: 6  
docker\_container\_mem: 35  
docker\_data: 3  
processes: 10  
procstat: 55  
disk: 7  
docker\_container\_blkio: 11  
Tags (est):  
io.kubernetes.container.hash: 1261  
io.kubernetes.container.name: 550  
vcs-ref: 17  
io.openshift.s2i.scripts-url: 2  
node\_name: 2  
path: 7  
engine\_host: 385  
Authoritative\_Registry: 1  
pod\_name: 12  
volume\_name: 3  
io.k8s.description: 13  
release: 13  
description: 2  
Release: 12  
vcs-type: 1  
io.openshift.tags: 12  
com.docker.compose.oneoff: 1  
hostname: 462  
io.kubernetes.pod.namespace: 271  
summary: 2  
exe: 2  
unit: 1  
license: 1  
interface: 1960  
authoritative-source-url: 1  
com.redhat.deployments-dir: 1  
container\_version: 599  
com.docker.compose.version: 1  
name: 469  
architecture: 1  
com.redhat.component: 11  
com.redhat.build-host: 11  
io.kubernetes.container.terminationMessagePath: 1  
io.kubernetes.pod.uid: 2504  
com.docker.compose.service: 4  
device: 656  
BZComponent: 10  
Component: 1  
PostgresVersion: 2  
cluster: 3  
version: 14  
com.redhat.dev-mode.port: 1  
io.kubernetes.pod.name: 2205  
io.kubernetes.pod.terminationGracePeriod: 4  
com.docker.compose.config-hash: 4  
datacenter: 3  
build-date: 34  
com.redhat.dev-mode: 1  
cpu: 185  
distribution-scope: 1  
com.docker.compose.container-number: 1  
container\_image: 389  
io.kubernetes.container.restartCount: 1337  
namespace: 5  
io.openshift.expose-services: 3  
fstype: 2  
Name: 10  
io.kubernetes.container.ports: 281  
io.k8s.display-name: 14  
vendor: 2  
process\_name: 9  
Build\_Host: 2  
Vendor: 2  
Version: 12  
com.docker.compose.project: 1  
Architecture: 1  
container\_name: 6200  
io.openshift.builder-version: 1  
Completed in 24.581871901s

=============================

influx\_inspect report -detailed /var/lib/influxdb/data/hosting/one\_week/238/  
File Series Load Time  
000000776-000000005.tsm 1095559 296.404829ms  
000000776-000000006.tsm 469821 130.299482ms

Statistics  
Series:  
Total (est): 1561417  
Measurements (est):  
kubernetes\_pod\_container: 143 (0%)  
kubernetes\_pod\_volume: 21 (0%)  
kubernetes\_system\_container: 44 (0%)  
net: 30566 (1%)  
netstat: 1388 (0%)  
processes: 1070 (0%)  
docker: 1178 (0%)  
docker\_container\_blkio: 557549 (35%)  
docker\_container\_cpu: 537433 (34%)  
kernel: 427 (0%)  
procstat: 7877 (0%)  
swap: 642 (0%)  
disk: 7672 (0%)  
docker\_container\_mem: 340009 (21%)  
docker\_metadata: 321 (0%)  
kubernetes\_node: 36 (0%)  
kubernetes\_pod\_network: 48 (0%)  
mem: 1070 (0%)  
system: 749 (0%)  
cpu: 21049 (1%)  
diskio: 42384 (2%)  
docker\_data: 321 (0%)  
Fields (est):  
netstat: 13  
procstat: 63  
docker\_container\_blkio: 11  
kernel: 4  
kubernetes\_node: 18  
kubernetes\_pod\_container: 13  
kubernetes\_system\_container: 11  
docker: 13  
docker\_data: 3  
kubernetes\_pod\_network: 4  
net: 117  
cpu: 10  
disk: 7  
docker\_container\_cpu: 9  
docker\_container\_mem: 35  
mem: 10  
system: 7  
diskio: 118  
docker\_metadata: 3  
kubernetes\_pod\_volume: 3  
processes: 10  
swap: 6  
Tags (est):  
fstype: 2  
path: 7  
Vendor: 2  
io.kubernetes.container.name: 540  
hostname: 564  
com.redhat.build-host: 11  
com.redhat.component: 11  
com.redhat.dev-mode.port: 1  
io.openshift.tags: 12  
BZComponent: 10  
engine\_host: 494  
Version: 10  
io.kubernetes.container.hash: 1170  
io.kubernetes.pod.uid: 1967  
io.openshift.expose-services: 3  
cpu: 208  
Component: 1  
build-date: 34  
distribution-scope: 1  
com.redhat.dev-mode: 1  
license: 1  
Architecture: 1  
unit: 1  
Name: 10  
io.k8s.display-name: 14  
version: 12  
com.docker.compose.oneoff: 1  
com.docker.compose.project: 1  
datacenter: 3  
io.kubernetes.pod.terminationGracePeriod: 4  
com.docker.compose.container-number: 1  
com.docker.compose.version: 1  
exe: 2  
process\_name: 12  
io.kubernetes.pod.name: 1829  
com.docker.compose.config-hash: 4  
vcs-ref: 17  
io.kubernetes.container.terminationMessagePath: 1  
io.openshift.s2i.scripts-url: 2  
volume\_name: 3  
name: 446  
Release: 12  
container\_image: 440  
io.openshift.builder-version: 1  
Authoritative\_Registry: 1  
io.k8s.description: 13  
release: 13  
summary: 2  
node\_name: 2  
namespace: 5  
device: 698  
container\_name: 7144  
container\_version: 691  
vendor: 2  
PostgresVersion: 2  
architecture: 1  
vcs-type: 1  
com.docker.compose.service: 4  
cluster: 3  
io.kubernetes.pod.namespace: 268  
interface: 2196  
io.kubernetes.container.ports: 166  
io.kubernetes.container.restartCount: 465  
com.redhat.deployments-dir: 1  
description: 2  
pod\_name: 12  
Build\_Host: 2  
authoritative-source-url: 1  
Completed in 19.121463128s

===================

We have a very bigh Kubernets based Docker platform and each node running multiple containers. The amount of new pods creation and deletion is also very high. I think that is the reason very high cardinality from docker plugin. How to fix or reduce the cardinality form docker input plug-in ?

your help is highly appreciated to fix as am facing very uncertanity with InfluxDB and my metrics solution is frequently doing down and not reliable although i gave 30 GB memory to InfluxDB container.

my current series is

SELECT numSeries FROM “\_internal”…“database” GROUP BY “database” ORDER BY desc LIMIT 1  
name: database  
tags: database=network  
time numSeries

* * *

1495595820000000000 0

name: database  
tags: database=hosting  
time numSeries

* * *

1495595820000000000 1252706

name: database  
tags: database=heapster  
time numSeries

* * *

1495595820000000000 185176

name: database  
tags: database=ech  
time numSeries

* * *

1495595820000000000 0

name: database  
tags: database=ceph  
time numSeries

* * *

1495595820000000000 342

name: database  
tags: database=capi  
time numSeries

* * *

1495595820000000000 1854

name: database  
tags: database=cae  
time numSeries

* * *

1495595820000000000 305

name: database  
tags: database=aci  
time numSeries

* * *

1495595820000000000 0

name: database  
tags: database=\_internal  
time numSeries

* * *

1495595820000000000 1486

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [May 25, 2017, 5:19pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/5 "2017-05-25T17:19:01Z")

</div>

Jason

Your help is appreciated. This issue for quite some causing trouble for me and unable to scale up the metrics platform.

Srinivas Kotaru

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [May 25, 2017, 6:04pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/6 "2017-05-25T18:04:47Z")

</div>

@Srinivas_Kotaru Are you running the TICK stack via the `tick-charts` repo? I maintain that repo and run it in a couple of environments. The extra cardinality is coming primarily from the additional tags added on the docker measurements. They come from the docker daemon. Add the following to your [`telegraf-ds/values.yaml` file](https://github.com/influxdata/tick-charts/blob/master/telegraf-ds/values.yaml):

```auto
config:
  inputs:
    docker:
      docker_label_exclude:
        - "annotation.kubernetes.io/*"
        - "io.kubernetes*"
        - "com.docker*"
        - "com.redhat.*"

```

That will eliminate the most egregious cardinality offenders.

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [May 25, 2017, 6:26pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/7 "2017-05-25T18:26:29Z")

</div>

@jackzampolin. Thanks for your reply. i am not using Helm package manager rather using direct images from DockerHub and customize the configuration as per my needs. All the core components like InfluxDB, telegraf and Grafana running as containers.

If you look at my telegraf configuration am already excluding all labels.

[[inputs.docker]]  
endpoint = “unix:///var/run/docker.sock"  
timeout = “30s"  
perdevice = true  
total = true  
docker\_label\_exclude = [”\*”]

Do I need exclude any more? Based on conversation in this thread with @jason, am thinking we should exclude taga also.

Any help is highly appreciated to reduce this docker cardinality issue

Srinivas Kotaru

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [May 25, 2017, 6:41pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/8 "2017-05-25T18:41:36Z")

</div>

@Srinivas_Kotaru Based on the output above it looks like those labels are still being written. What version of telegraf are you running? The label exclude feature for docker wasn’t merged until 1.3.

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [May 25, 2017, 11:01pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/9 "2017-05-25T23:01:42Z")

</div>

@jackzampolin I’m using latest telegraf 1.3.0

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [May 26, 2017, 4:47pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/10 "2017-05-26T16:47:21Z")

</div>

@Srinivas_Kotaru Have you tried to specifically exclude the tags? I’ve had success doing that on my cluster.

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [May 26, 2017, 6:41pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/11 "2017-05-26T18:41:37Z")

</div>

@jackzampolin No I didn’t tried yet and that is what i want to try to reduce amount of data coming to InfluxDB. But the confusion is what tags need to exclude? I’m using namespace and pods and container tags exclusive. is there anyway to identify which tags are causing more problem and see whether am using them or not in my Grafana graphs and alerts?

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [May 26, 2017, 8:20pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/12 "2017-05-26T20:20:39Z")

</div>

@Srinivas_Kotaru The output you posted above contains that information.

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [June 16, 2017, 10:59pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/13 "2017-06-16T22:59:15Z")

</div>

@jackzampolin  
This seems my problems with InfluxDB is never ending. Today I received this message from all of my telegraf agents.

2017-06-16T00:35:20Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster  
2017-06-16T00:35:34Z E! InfluxDB Output Error: Response Error: Status Code [400], expected [204], [partial write: max-values-per-tag limit exceeded (100026/100000): measurement=“docker\_container\_blkio” tag=“container\_name” value=“k8s\_kong-app.251f7133\_kong-app-2645397686-gdof2\_coi-iamservices-poc\_23f8e542-51f9-11e7-b69f-005056ac69a9\_105a76e2” dropped=15]  
2017-06-16T00:35:34Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster  
2017-06-16T00:35:45Z E! InfluxDB Output Error: Response Error: Status Code [400], expected [204], [partial write: max-values-per-tag limit exceeded (100026/100000): measurement=“docker\_container\_blkio” tag=“container\_name” value=“k8s\_kong-app.251f7133\_kong-app-2645397686-gdof2\_coi-iamservices-poc\_23f8e542-51f9-11e7-b69f-005056ac69a9\_105a76e2” dropped=15]  
2017-06-16T00:35:45Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster  
2017-06-16T00:35:51Z E! InfluxDB Output Error: Response Error: Status Code [400], expected [204], [partial write: max-values-per-tag limit exceeded (100026/100000): measurement=“docker\_container\_blkio” tag=“container\_name” value=“k8s\_kong-app.251f7133\_kong-app-2645397686-gdof2\_coi-iamservices-poc\_23f8e542-51f9-11e7-b69f-005056ac69a9\_105a76e2” dropped=15]  
2017-06-16T00:35:51Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster  
2017-06-16T00:36:04Z E! InfluxDB Output Error: Response Error: Status Code [400], expected [204], [partial write: max-values-per-tag limit exceeded (100026/100000): measurement=“docker\_container\_blkio” tag=“container\_name” value=“k8s\_kong-app.251f7133\_kong-app-2645397686-gdof2\_coi-iamservices-poc\_23f8e542-51f9-11e7-b69f-005056ac69a9\_105a76e2” dropped=15]  
2017-06-16T00:36:04Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster  
2017-06-16T00:36:10Z E! InfluxDB Output Error: Response Error: Status Code [400], expected [204], [partial write: max-values-per-tag limit exceeded (100026/100000): measurement=“docker\_container\_blkio” tag=“container\_name” value=“k8s\_kong-app.251f7133\_kong-app-2645397686-gdof2\_coi-iamservices-poc\_23f8e542-51f9-11e7-b69f-005056ac69a9\_105a76e2” dropped=15]  
2017-06-16T00:36:10Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster  
2017-06-16T00:36:23Z E! InfluxDB Output Error: Response Error: Status Code [400], expected [204], [partial write: max-values-per-tag limit exceeded (100026/100000): measurement=“docker\_container\_blkio” tag=“container\_name” value=“k8s\_kong-app.251f7133\_kong-app-2645397686-gdof2\_coi-iamservices-poc\_23f8e542-51f9-11e7-b69f-005056ac69a9\_105a76e2” dropped=15]  
2017-06-16T00:36:23Z E! Error writing to output [influxdb]: Could not write to any InfluxDB server in cluster

for time being in increased the count and put 0 as unlimited value

why docker input plug-in causing this much problem? I already excluded all the labels. What further tuning is required?

Srinivas Kotaru

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [June 19, 2017, 10:52pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/14 "2017-06-19T22:52:21Z")

</div>

@jackzampolin any ideas guys before my InfluxDB go down again?

Srinivas Kotaru

---

<div class="post-metadata">

**Author:** ![jackzampolin](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/jackzampolin/32/5_2.png) [@jackzampolin](https://community.influxdata.com/u/jackzampolin)\
**Post date:** [June 19, 2017, 11:03pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/15 "2017-06-19T23:03:26Z")

</div>

@Srinivas_Kotaru The `container_id` is also very high cardinality depending on your deployment. I would suggest moving the database to a larger machine, downsampling with continuous queries or kapacitor, or moving to a scale out cluster. I would guess however that you have a decent amount of headroom. An 8-16GB RAM instance should be able to handle ~2M series with no problem.

---

<div class="post-metadata">

**Author:** ![Srinivas\_Kotaru](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@Srinivas\_Kotaru](https://community.influxdata.com/u/Srinivas_Kotaru)\
**Post date:** [June 19, 2017, 11:41pm UTC](https://community.influxdata.com/t/influxdb-tuning/1017/16 "2017-06-19T23:41:55Z")

</div>

Thanks for response. my platform is Kubernetes based cluster and already allocated 30GB memory to influxDB. i am wondering this much memory is really required for InfluxDB for a decent size cluster and wondering what about if my platform expand with more nodes?

is anything we can do to tune my docker plugin data? I mean reducing unnecessary tags or series in the DB. If you look at my config, I already using docker\_label\_exclude = ["\*"]. Do I still need to do anything?

Any help in this regard is appreciated? I am frequently facing DB down and causing false alarms from Grafana.

Srinivas Kotaru
