action #110680
closed
coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #92854: [epic] limit overload of openQA webUI by heavy requests
Overview page shouldn't allow long-running requests without limits size:M
Added by livdywan over 2 years ago.
Updated over 2 years ago.
Category:
Feature requests
Description
Motivation¶
To resolve #106759#note-37 the endpoint /tests/overview
needs a (reasonably high) limit on the number of jobs to prevent heartbeat and reverse proxy timeouts from being triggered.
Acceptance criteria¶
- AC1: /tests/overview requests are no longer able to block the prefork worker process for more than 400 seconds
- AC2: No limits are hard-coded (e.g. the limit can be configured in openqa.ini)
Suggestions¶
- Add a hard limit on the number of database rows
- Render an error message e.g. "Only n results included, please narrow down your search parameters"
- Use the
/tests/overview?version=Tumbleweed&groupid=24
dataset for testing
- Copied from action #106759: Worker xyz has no heartbeat (400 seconds), restarting repeatedly reported on o3 size:M added
- Project changed from openQA Infrastructure (public) to openQA Project (public)
- Due date deleted (
2022-05-13)
- Category set to Feature requests
- Parent task set to #92854
Been some time since i worked on the frontend.
- Copied from deleted (action #106759: Worker xyz has no heartbeat (400 seconds), restarting repeatedly reported on o3 size:M)
- Blocked by action #106759: Worker xyz has no heartbeat (400 seconds), restarting repeatedly reported on o3 size:M added
- Blocked by deleted (action #106759: Worker xyz has no heartbeat (400 seconds), restarting repeatedly reported on o3 size:M)
- Blocks action #106759: Worker xyz has no heartbeat (400 seconds), restarting repeatedly reported on o3 size:M added
- Related to action #97190: Limit size of initial requests everywhere, e.g. /, /tests, etc., over webUI and API added
- Status changed from Workable to In Progress
I have replicated the issue locally with a copy of O3.
- Due date set to 2022-06-07
Setting due date based on mean cycle time of SUSE QE Tools
Side note: the actual cause for prefork worker processes blocking everything and getting killed was the query that retrieves the comments for the jobs on the /tests/overview
page.
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- Status changed from Resolved to Feedback
- Status changed from Feedback to Resolved
- Due date deleted (
2022-06-07)
Also available in: Atom
PDF