Run DB Checks Fails with 504 Gateway timeout with PMM-Server monitoring high number of DB Instances
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
Attachments
3
- 08 Oct 2021, 02:37 PM
- 08 Oct 2021, 02:28 PM
- 08 Oct 2021, 02:27 PM
is duplicated by
Smart Checklist
Activity
Show:
Done
Details
Details
Assignee
Artem Gavrilov
Artem GavrilovReporter
Puneet Kala
Puneet KalaPriority
MediumComponents
Labels
Needs QA
Yes
Fix versions
Story Points
0.5
Affects versions
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created October 8, 2021 at 2:35 PM
Updated March 6, 2024 at 2:02 AM
Resolved January 26, 2022 at 11:24 AM
User Impact: For a User using PMM for monitoring a high number of DB instances, it might not really be possible to run the DB checks on all monitored Instances using Run DB Checks Button.
During the Performance Testing Instance Setup for PMM 2.23.0 RC We tried to run DB Checks on a PMM-Server instance monitoring roughly 380 Services
The user sees a totally unfriendly error on the UI "Unknown Error" and the request times out.
At the end of the request we show them, DB checks were executed Successfully which is more confusing.
Expected Behaviour: Request timeout error should be avoided, maybe we could break the requests into smaller.
At the moment, we don't have a way to give users a better view to watch progress for these checks running on monitored DB services.