Actions
action #25960
closed[tools][sprint 201710.2][sprint 201711.1] Investigate/Optimize messages sent from Workers to WebSockets Server
Start date:
2017-10-11
Due date:
% Done:
90%
Estimated time:
Description
Currently Workers are sending keepalives to the server to avoid being turned down - with the changes to the scheduler the message became also a way to update the latest seen time of the worker (instead of doing nothing) - this now can be included in the worker_status message, and so we can get rid of the keepalive message (deprecating it for good).
A preliminar work on this is: https://github.com/os-autoinst/openQA/pull/1436 - the proposal is about to frame-slotting the time window where a worker sends the message, to avoid overlaps between different workers messages as much as possible.
Updated by EDiGiacinto over 6 years ago
- Subject changed from [tools] Investigate/Optimize messages sent from Workers to WebSockets Server to [tools][sprint 201710.2] Investigate/Optimize messages sent from Workers to WebSockets Server
- Assignee set to EDiGiacinto
Updated by EDiGiacinto over 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 70
PR: https://github.com/os-autoinst/openQA/pull/1486 - Needs testing on staging still
Updated by szarate over 6 years ago
- Subject changed from [tools][sprint 201710.2] Investigate/Optimize messages sent from Workers to WebSockets Server to [tools][sprint 201710.2][sprint 201711.1] Investigate/Optimize messages sent from Workers to WebSockets Server
Updated by EDiGiacinto over 6 years ago
- Status changed from In Progress to Feedback
- % Done changed from 70 to 90
Updated by szarate 9 months ago
- Related to coordination #135122: [epic] OSD openQA refuses to assign jobs, >3k scheduled not being picked up, no alert added
Actions