Actions
Bug #20533
openBetter handling of request surges when canceling a large workflow
Start date:
Due date:
% Done:
0%
Estimated time:
(Total: 0.00 h)
Story points:
-
Description
Specific test case: running a workflow with 100s of containers and then canceling them all at once leads to a massive surge of requests to the API server as all the containers finalize all at once.
Want to test ways that we can mitigate this traffic surge so that:
- all the containers finalize without fatal 503 errors (#20540, #20541)
- the workbench remains responsive (at least for GET requests during this time)
- evaluate configuration changes
- load balancing #20539
- controller request prioritization #20602
- Send out cancellations at a slower rate than whatever it's doing right now
Related issues
Updated by Peter Amstutz 9 days ago
- Target version changed from To be groomed to To be scheduled
Updated by Peter Amstutz 9 days ago
- Target version changed from To be scheduled to Development 2023-06-07
Updated by Peter Amstutz 8 days ago
- Description updated (diff)
- Subject changed from Better handling of request surges to Better handling of request surges when canceling a large workflow
Updated by Peter Amstutz 1 day ago
- Related to Story #20599: Scaling to 1000s of concurrent containers added
Updated by Peter Amstutz 1 day ago
- Related to Story #20602: Prioritize requests made by workbench 2 added
Updated by Peter Amstutz 1 day ago
- Target version changed from Development 2023-06-07 to To be groomed
Actions