action #23320
closedopenQA Tests (public) - action #20378: [tools]Too many 502 on openqa
[tools][sprint 201709.2][sprint 201710.1][sprint 201710.2] move locks/mutexes/barriers/job restarts out of scheduler
100%
Description
With the new scheduler logic, we now use the dbus service to schedule: this operation could keep busy the dbus service for long time, delaying access to locks, mutexes, barriers and job restarts.
We should move those access to resources in another process (and hence makes sense to me to have a new "ResourceAllocator" service) before it could become a real problem
Updated by EDiGiacinto over 7 years ago
- Project changed from openQA Tests (public) to openQA Project (public)
Updated by okurz over 7 years ago
- Related to action #23378: [tools][sprint 201709.1] Enhancement and cleanup of "assigned" state added
Updated by EDiGiacinto over 7 years ago
temporary workaround applied in production: https://github.com/os-autoinst/openQA/pull/1433
we may bump those values as well to reduce the websocket server load caused also by dispatching jobs over ws.
Updated by nicksinger over 7 years ago
- Copied to action #23536: [tools] org.freedesktop.DBus.Error.NoReply: Did not receive a reply. appreas regularly in openQA logs added
Updated by nicksinger over 7 years ago
- Copied to deleted (action #23536: [tools] org.freedesktop.DBus.Error.NoReply: Did not receive a reply. appreas regularly in openQA logs)
Updated by szarate over 7 years ago
- Subject changed from [tools] move locks/mutexes/barriers out of scheduler to [tools][Sprint 1] move locks/mutexes/barriers out of scheduler
- Category set to Feature requests
- Assignee set to EDiGiacinto
- Target version set to Milestone 10
Updated by szarate over 7 years ago
- Subject changed from [tools][Sprint 1] move locks/mutexes/barriers out of scheduler to [tools][sprint 201709.2] move locks/mutexes/barriers out of scheduler
Updated by EDiGiacinto over 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 70
Bits are already there, needs to be tested widely, since are changing also our build matrix. Will proceed to create a separate branch for the feature right after everything is good to go.
Updated by szarate over 7 years ago
- Subject changed from [tools][sprint 201709.2] move locks/mutexes/barriers out of scheduler to [tools][sprint 201709.2][sprint 201710.1] move locks/mutexes/barriers out of scheduler
Updated by EDiGiacinto about 7 years ago
- % Done changed from 70 to 90
For reference, PR : https://github.com/os-autoinst/openQA/pull/1467
Updated by EDiGiacinto about 7 years ago
- Subject changed from [tools][sprint 201709.2][sprint 201710.1] move locks/mutexes/barriers out of scheduler to [tools][sprint 201709.2][sprint 201710.1][sprint 201710.2] move locks/mutexes/barriers out of scheduler
Updated by EDiGiacinto about 7 years ago
- Subject changed from [tools][sprint 201709.2][sprint 201710.1][sprint 201710.2] move locks/mutexes/barriers out of scheduler to [tools][sprint 201709.2][sprint 201710.1][sprint 201710.2] move locks/mutexes/barriers/job restarts out of scheduler