Celery task queues are not deleted
Bug #893113 reported by
Muharem Hrnjadovic
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenQuake (deprecated) |
Fix Released
|
High
|
Muharem Hrnjadovic | ||
Bug Description
The celery task queues are not deleted after the task results are collected. This results in a high number of queues (> 20000) and eventually leads to RabbitMQ failures.
| Changed in openquake: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Muharem Hrnjadovic (al-maisan) |
| milestone: | none → 0.4.6 |
| Changed in openquake: | |
| status: | Confirmed → In Progress |
| tags: | added: celery |
Revision history for this message
| Muharem Hrnjadovic (al-maisan) wrote | #1 |
| Changed in openquake: | |
| status: | In Progress → Fix Committed |
| Changed in openquake: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This issuse was resolved with the upgrade to celery-2.4.2; The max. number of task queues is now peaking at approx. 6800.