Actions
action #136961
openLower timeouts for HTTP requests from scheduler to websocket
Start date:
Due date:
2023-09-25 (about 7 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
Actions