Done
Details
Details
Assignee
Nurlan Moldomurov
Nurlan MoldomurovReporter
Sergey Pronin
Sergey Pronin(Deactivated)Priority
Components
Needs QA
Yes
Fix versions
Story Points
3
Smart Checklist
Smart Checklist
Created March 10, 2021 at 1:29 PM
Updated April 15, 2025 at 10:19 AM
Resolved December 15, 2021 at 1:52 PM
This improvement request comes from this bug: https://jira.percona.com/browse/K8SPXC-585
Issue:
If pmm-client cannot connect to pmm-server for any reason (network glitch, wrong password), pmm-client container crashes.
This means that monitoring server stability can affect the stability of the database cluster.
Desired behavior:
Container should not crash, but just throw an error.
Good example - mongodb-exporter. If it cannot connect to MongoDB database:
it still runs
on metrics page it tells that it cannot connect to MongoDB and states the reason
Default entrypoint shouldn't exit with error, but waiting in infinite loop with trying to apply failed commands and provide logs to show issue.
How to test:
Use FB from https://github.com/Percona-Lab/pmm-submodules/pull/1924
Enable DBaaS
Set wrong public address in settings
Create new DB Cluster
Check that DB Cluster isn't failed because of failing pmm-client