Issue #110: Implement some rate-limiting or throttling for the scheduler. - fm-orchestrator

fm-orchestrator

#110 Implement some rate-limiting or throttling for the scheduler.

Closed Dec 16, 2016 Opened Oct 21, 2016 by ralph.

We can't have the backend schedule 2600 builds for base-runtime.. we should do some throttling or rate-limiting (configurable) so we don't swamp koji.

ralph commented Oct 21, 2016

This may be a duplicate of #109. The work proposed there may be sufficient.

If it is not, then we may need to do something further here like koschei does (where it only allows ~4 of its builds to be submitted at a given time).

karsten commented Nov 4, 2016

I've started a scratch build when rida had already put >1000 build into the build queue. My build got picked up almost immediately, bypassing all the module build requests except those that were already building. I think the PR#109 solution works and this can be closed

ralph commented Nov 9, 2016

Thanks @karsten. Feedback from @ausil suggests that we should still implement this. They would like the ability to turn down the module build submission rate significantly when they are trying to debug something in koji and want to reduce noise.

ralph commented Nov 10, 2016

Definitely look to the code of koschei for inspiration here.

https://github.com/msimacek/koschei/blob/master/koschei/backend/services/scheduler.py#L148-L152

ralph commented Dec 16, 2016

This was fixed in #184.

@ralph changed the status to Closed

Dec 16, 2016

mikem commented Apr 21, 2026

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/mbs/issues/110

Please continue any further discussion there.