Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiples netbox-rq workers #5927

Closed
Trunkol opened this issue Mar 4, 2021 · 3 comments
Closed

Multiples netbox-rq workers #5927

Trunkol opened this issue Mar 4, 2021 · 3 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity

Comments

@Trunkol
Copy link

Trunkol commented Mar 4, 2021

Environment

  • Python version: 3.8.5
  • NetBox version: 2.9.4

Proposed Functionality

The way that netbox-rq service it's named today, we are able to get only one worker at a time. Based on RQ documentation we should just spawn another process using systemctl and the units files templates.

This will touch on the unit file name and perhaps the description.

Use Case

If you wanna multiples workers consuming from a queue and perhaps some jobs take some considerable amount of time.

@jsenecal
Copy link
Contributor

This comment is based on my experience with netbox 2.9.10 -

Netbox is currently unable to handle more than one worker as the only available result for a given task is the latest one AFAIK.
This, I believe would require an overhaul of how the scripts are being run and their results accessed.

@github-actions
Copy link
Contributor

github-actions bot commented May 3, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label May 3, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Jun 2, 2021

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions github-actions bot closed this as completed Jun 2, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending closure Requires immediate attention to avoid being closed for inactivity
Projects
None yet
Development

No branches or pull requests

2 participants