Actions
action #136961
openLower timeouts for HTTP requests from scheduler to websocket
Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
Due date:
2023-09-25 (about 15 months late)
% Done:
0%
Estimated time:
Description
Observation¶
- User reports on September 4 about few running jobs
Questions¶
- Why did the scheduler not complain that it was blocked for too long or is too slow to finish within timeout?
- There were no warnings because of the very long inactivity timeout of 10 minutes for HTTP requests from the scheduler to the websocket server -> TODO look into shorter timeouts and a good error message
Updated by tinita about 1 year ago
- Copied from action #135239: Conduct lessons learned "Five Why" analysis for "OSD openQA refuses to assign jobs, >3k scheduled not being picked up, no alert" size:M added
Actions