Details
-
Bug
-
Status: Done
-
High
-
Resolution: Fixed
-
2.0.0-beta7, 2.1.0
-
5
-
Platform Sprint 5, Platform Sprint 6, Platform Sprint 7, Platform Sprint 8, Platform Sprint 9, Platform Sprint 10
-
Yes
-
Yes
-
Yes
-
No
Description
STR
- Install PMM2 (201909051008)
- install pmm2-client
- Add MongoDb to PMM2
pmm-admin add mongodb --use-profiler localhost:27017 DefaultNoCluster
- Check pmm-agent process
Given result:
CPU usage of pmm-agent is more 50%
I re-checked on servers with Replicaset Mongodb and single MongoDB, but the problem with CPU appears for all
[[email protected] ~]$ pmm-admin --version ProjectName: pmm-admin Version: 2.0.0-beta7 PMMVersion: 2.0.0-beta7 Timestamp: 2019-09-05 10:09:39 (UTC) FullCommit: ec4a02044cfd73da53067564b651bbe8ab4e8ad4 [[email protected] ~]$ pmm-agent --version ProjectName: pmm-agent Version: 2.0.0-beta7 PMMVersion: 2.0.0-beta7 Timestamp: 2019-09-05 10:10:00 (UTC) FullCommit: 4cdd9420c0205120b9d218525c4e63e4a82dafd7
Steps
- Remove code that is clearly not used.
- Add logging, especially around connection/disconnection.
- Add pprof labels: https://rakyll.org/profiler-labels/
- Try to find and fix this bug.
Attachments
Issue Links
- is caused by
-
PMM-3950 Refactor/cleanup qan-mongodb-profiler
-
- Done
-
