dramatiq.worker.busy

Workers currently processing

Dimensions:None

Available on:

Number of workers currently processing messages

Dimensions:None

Sources

Technical Annotations (13)

Configuration Parameters (2)

queue_namerecommended: high-priority, default, low-priority, bulk

Separate queues by priority to prevent head-of-line blocking

dramatiq_queue_prefetchrecommended: 1

For long-running tasks requiring even distribution; default ~1000 optimizes throughput

Error Signatures (2)

Pushing message '.*' onto work queue.log pattern

Received message .* with id '.*'.log pattern

CLI Commands (4)

dramatiq tasks --queues high-priority --threads 8remediation

dramatiq tasks --queues default low-priority --threads 4remediation

dramatiq an_app --queues defaultremediation

dramatiq an_app --queues ui-blockingremediation

Technical References (5)

work queueconcepttime.sleepcomponentkafka providercomponentworker.pyfile pathqueue prefetchconcept

Worker pool exhaustion from blocking retry delays prevents message processingcritical

▸

Millisecond to second conversion bug causes 1000x longer retry delayscritical

▸

Missing 'Received message' log indicates worker pool exhaustionwarning

▸

Concurrent actor execution overwhelms database and external serviceswarning

▸

Worker thread pool exhaustion delays high-priority taskswarning

▸

Worker prefetch monopolizes queue in distributed setupcritical

▸

Slow actors on shared queues block high-priority taskswarning

▸