Multiple rq-workers, queue priority

[julianstolp]

We have a cronjob which queues a script to scan a switch. It is done for all of our switches every night. It takes around 6 hours to complete with one worker. In between these 6 hours all manual started scripts by a user are queued behind and are not executed directly. So I searched for a way to spawn more workers and set a low priority to the scan.

Worker
I tried as described in #5927 (Renaming netbox-rq.service to [email protected], perform a systemctl daemon-reload, start multiple workers with a number behind @) which seems works fine.

Are there any possible sideeffects like datacorruption or so?

Queue
In the issue #6651 it's stated that it is possible for plugins to access high or low priority queue. Is this also possible for custom scripts to be queued in high?

Thanks!

[julianstolp]

Does anyone have an answer to this topic?

[mtinberg]

My understanding is that the workers pick up their jobs from a queue in redis so it's specifically designed for there to be multiple possible workers and only one will pick up the queued job. I have workers on different servers and that has been fine (as long as they both have the same code for Scripts and Reports) — Mark Tinberg ***@***.***> Division of Information Technology-Network Services University of Wisconsin-Madison

…

________________________________ From: Bierfass ***@***.***> Sent: Friday, July 8, 2022 4:27 AM To: netbox-community/netbox ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [netbox-community/netbox] Multiple rq-workers, queue priority (Discussion #9626) Does anyone have an answer to this topic? — Reply to this email directly, view it on GitHub<#9626 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAS7UMYG6CKJDYOATMPZZOLVS7X7VANCNFSM52FMZ6JQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>