Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non optimal default behavior #401

Closed
nunokisc opened this issue Jul 2, 2019 · 1 comment · Fixed by #406
Closed

Non optimal default behavior #401

nunokisc opened this issue Jul 2, 2019 · 1 comment · Fixed by #406
Assignees
Labels

Comments

@nunokisc
Copy link

nunokisc commented Jul 2, 2019

Host operating system:

Linux 3.10.0-962.3.2.lve1.5.25.10.el7.x86_64 #1 SMP Wed May 29 04:37:40 EDT 2019 x86_64 x86_64 x86_64 GNU/Linux
or
Linux 2.6.32-896.16.1.lve1.4.49.el6.x86_64 #1 SMP Fri Jan 5 05:15:23 EST 2018 x86_64 x86_64 x86_64 GNU/Linux

mysqld_exporter version:

mysqld_exporter, version 0.11.0 (branch: HEAD, revision: 5d71796)
build user: root@3d3ff666b0e4
build date: 20180629-15:00:35
go version: go1.10.3

MySQL server version

Databases:

  • Mysql between 5.6 and 5.7
  • MariaDB >10

mysqld_exporter command line flags

Default

What did you do that produced an error?

I work at a company that provides internet services and we start installing monitoring with prometheus and everything went well until we decided to start installing the mysqld exporters and configure them on prometheus. The prometheus began to consume more than 64gb of memory in a few minutes and did not stop growing.
We came to find out that the problem was with the "collect.info_schema.tables" parameter that is enabled by default. We set up 120 machines with approximately 50000 tables in 700db's on each machine it became tricky for prometheus to process all this information.
This issue is only to alert to the fact that it may be dangerous to let this parameter enable by default, because with this parameter enable in the datacenter dimension we have, prometheus simply does not work and with this parameter disable prometheus works as if nothing were.

With this parameter enable we reach 9 million head times series and with the parameter disable we have around 250 thousand head time series. Now only consume about 2gb of memory.

@SuperQ
Copy link
Member

SuperQ commented Jul 10, 2019

Yes, that's a bit over the top. 😄 I agree, this collector should be disabled by default.

@SuperQ SuperQ added the bug label Jul 10, 2019
@SuperQ SuperQ self-assigned this Jul 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants