starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Multiples netbox-rq workers #4629

New Issue
Closed
opened 2025-12-29 18:38:28 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:38:28 +01:00
Owner
Copy Link

Originally created by @Trunkol on GitHub (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.

Originally created by @Trunkol on GitHub (Mar 4, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.8.5 * NetBox version: 2.9.4 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality The way that [netbox-rq service](https://github.com/netbox-community/netbox/blob/develop/contrib/netbox-rq.service) it's named today, we are able to get only one worker at a time. Based on [RQ documentation](https://python-rq.org/patterns/systemd/) we should just spawn another process using `systemctl` and the [units files templates](https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files#creating-instance-units-from-template-unit-files). This will touch on the unit file name and perhaps the description. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case If you wanna multiples workers consuming from a queue and perhaps some jobs take some considerable amount of time.
adam added the pending closure label 2025-12-29 18:38:28 +01:00
adam closed this issue 2025-12-29 18:38:28 +01:00
adam commented 2025-12-29 18:38:28 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Mar 18, 2021):

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.

@jsenecal commented on GitHub (Mar 18, 2021): 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.
adam commented 2025-12-29 18:38:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (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[bot] commented on GitHub (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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:38:29 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (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[bot] commented on GitHub (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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4629
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?