Project

General

Profile

Actions

action #27454

closed

coordination #32851: [tools][EPIC] Scheduling redesign

[tools][scheduling] Worker's seen DB field is ignored by WebSocket server when checking for stale jobs

Added by EDiGiacinto over 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2018-05-05
Due date:
% Done:

0%

Estimated time:

Description

Worker's status are updated also via different routes ( e.g. while updating job status [1] ) but in WebSocket server we check for stale jobs using another field that is updated in the WebSocket server context [1] and used later to reap jobs that belongs to inactive workers [3].
We should unify the way we check for the worker seen status, possibly using the DB as a reference or jobs could be marked as incomplete if a blocking operation on the worker side occurs ( e.g. during cache setup phase, rsync calls, ecc.. ).

  1. https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Schema/Result/Jobs.pm#L1357
  2. https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/WebSockets/Server.pm#L204
  3. https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/WebSockets/Server.pm#L348

Related issues 1 (0 open1 closed)

Related to openQA Project - action #25970: Profile/Optimize _workers_checker in WebSockets serverResolved2017-10-11

Actions
Actions

Also available in: Atom PDF