Details
-
Bug
-
Status: Done
-
High
-
Resolution: Fixed
-
None
-
0
-
Yes
-
Yes
-
[obsolete] Server Features
Description
User Impact:
DOD:
User impact:
after removing services , agent continue to consume resources on DB server and victoriametrics still collect data from exporters.
--------
Based on code it looks like we don't stop agents when we remove Services or Nodes in force mode using inventory API. Also we don't remove them from prometheus config.
Steps to reproduce:
- Setup PMM Server and pmm-agent
- Run MySQL Server
- Add new service via `pmm-admin add mysql` command
- Delete MySQL service via `pmm-admin inventory remove service` with --force flag.
- Run `ps -ax | grep mysqld_exporter` and check there is no mysqld_exporter
- Check that /etc/victoriametrics-promscrape.yml doesn't have scrape config for deleted exporter
Actual result;
After removing service with force flag all agents related to the service are not removed from VictoriaMetrics config.
After removing node with force flag all agents related to the service are not removed from VictoriaMetrics config.
Processes related to agents are not stopped after we remove them from DB.
Expected result:
After removing service with force flag all agents related to the service should be removed from VictoriaMetrics config.
After removing node with force flag all agents related to the service should be removed from VictoriaMetrics config.
Processes related to agents are stopped after we remove them from DB.
Workaround:
Send empty request to UpdateSettings API.
Details:
Attachments
Issue Links
- relates to
-
PMM-6295 Unclear/Incorrect statuses of the pmm-agent when Agent or PMM server went down
-
- Done
-