Redis Queue is populated with thousands of jobs after the custom script has been successfully completed! #17925
Replies: 3 comments 3 replies
-
The problem is likely in your script, can you show it? A single custom script should create a single job. |
Beta Was this translation helpful? Give feedback.
-
Most likely reason is that you have an event rule created for the device model, so each time you edit a device in the script, the event rule triggers a new script execution. |
Beta Was this translation helpful? Give feedback.
-
Hello, do you handle script scheduling? I have scripts scheduled to run every three hours, but for some reason—likely related to Redis—they started multiplying and overwhelming the workers with thousands of jobs. I haven’t been able to figure out the cause. The scripts execute normally regardless of the changes made to them, and they also run fine when scheduled. However, occasionally, they begin multiplying jobs by the second. |
Beta Was this translation helpful? Give feedback.
-
Hi,
My NetBox version is 4.1.6. I have written a custom script which updates more than 6000 NetBox devices.
When I run the script, the memory consumption of the NetBox server keeps increasing till no memory is availabe and it eventually makes the NetBox unresponsive!
Besides, when the script has successfully been completed, the Redis Queue is populated with thousands of jobs! And I have to wait for about 40 minutes for the queue to be cleared or I have to manually clear the queue!
Any idea what is causing the above issues?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions