Project

General

Profile

Actions

action #168502

closed

coordination #110833: [saga][epic] Scale up: openQA can handle a schedule of 100k jobs with 1k worker instances

coordination #157669: websockets+scheduler improvements to support more online worker instances

Check for high websockets load on o3 2024-10-20

Added by okurz about 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-10-20
Due date:
% Done:

0%

Estimated time:

Actions #1

Updated by okurz about 2 months ago

  • Status changed from New to Resolved

I looked through the log files on o3 for 2024-10-20 and found nothing out of the ordinary. Checked websockets and scheduler log archives. There were some mentions of aarch32 and aarch64 jobs like

[2024-10-20T10:16:16.411982Z] [debug] [pid:8025] Skipping 77 jobs because of no free workers for requested worker classes (qemu_aarch64:63,qemu_aarch64,tap:10,heavyload,s390x-zVM:2,s390x-zVM,tap:2)
[2024-10-20T10:16:16.414968Z] [debug] [pid:8025] Need to schedule 2 parallel jobs for job 4579724 (with priority 145)
[2024-10-20T10:16:37.037850Z] [debug] [pid:8025] Scheduling: Free workers: 262/464; Scheduled jobs: 79
[2024-10-20T10:16:37.152391Z] [debug] [pid:8025] Skipping 77 jobs because of no free workers for requested worker classes (qemu_aarch64:63,qemu_aarch64,tap:10,heavyload,s390x-zVM:2,s390x-zVM,tap:2)

but I assume that's ok.

Actions #2

Updated by okurz about 2 months ago

  • Parent task set to #157669
Actions

Also available in: Atom PDF