action #164284
closed
[FIRING:1] worker-arm1 (worker-arm1: System load alert openQA worker-arm1 salt system_load_alert_worker-arm1 worker) size:S
Added by livdywan 9 months ago.
Updated 8 months ago.
Category:
Regressions/Crashes
- Priority changed from Normal to High
- Target version set to Ready
- Subject changed from [FIRING:1] worker-arm1 (worker-arm1: System load alert openQA worker-arm1 salt system_load_alert_worker-arm1 worker) to [FIRING:1] worker-arm1 (worker-arm1: System load alert openQA worker-arm1 salt system_load_alert_worker-arm1 worker) size:S
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to livdywan
- Description updated (diff)
- Status changed from In Progress to Feedback
I wonder if we might need to look closer into what causes this. We're having a 48 core CPU here not being able to handle 10 worker-instances which seems odd to me. But it might be expected if each instance requires a lot of resources (which I haven't checked yet)
- Due date set to 2024-08-12
nicksinger wrote in #note-5:
I wonder if we might need to look closer into what causes this. We're having a 48 core CPU here not being able to handle 10 worker-instances which seems odd to me. But it might be expected if each instance requires a lot of resources (which I haven't checked yet)
CRITICAL_LOAD_AVG_THRESHOLD: 16
I was made aware that we have this feature, hence changing to this instead of reducing the number of workers.
- Due date deleted (
2024-08-12)
- Status changed from Feedback to Resolved
- Copied to action #179497: [FIRING:1] worker-arm1 (worker-arm1: System load alert openQA worker-arm1 salt system_load_alert_worker-arm1 worker) added
Also available in: Atom
PDF