Job queues: Celery task queues
If you’re running a combination of long and short running jobs, you may find that your queue is becoming full and jobs are taking a long time to start. This problem can usually be resolved by separating your long and short jobs into distinct Celery queues so that long running jobs don’t block short jobs. New queues can be used in Nautobot by starting a worker process listening on that queue. You can select any name you would like for your queue, but Nautobot’s default queue is named default
. Here’s an example of how you can start two Celery workers on the same server listening to different queues:
nautobot-server celery worker \Â Â Â Â --loglevel INFO \ Â Â Â Â --concurrency 10 \ Â Â Â Â --queues slow \ Â Â Â Â --hostname 'worker1@%%h' nautobot-server celery worker \ Â Â Â Â --loglevel INFO \ Â Â Â Â --concurrency 4...