action #157690
Updated by okurz 3 months ago
## Motivation
As observed in #157666 we seem to have a problem when too many openQA workers are connected at the same time. Similar to the global job limit in #129619 we should add a simple, configurable global limit of how many workers can be online (or registered?) at the same time to one openQA instance.
## Acceptance criteria
* **AC1:** A KISS configurable for number of online workers exists
* **AC2:** Rejected openQA workers exceeding the mentioned limit explicitly log or fail that situation
## Suggestions
* In the openQA scheduler (or websockets?) reject openQA worker registration or handling if a global, configurable limit is exceeded
* Select a sensible default, e.g. 1k
* Explicitly log or fail the openQA worker if rejected. A worker could be registered and be tracked as "offline" while rejected and not connected with at best an error message visible in the webUI. If too complicated start with something simpler, e.g. fatal fails of the worker instance.
Back