Closed
Bug 1228171
Opened 10 years ago
Closed 7 years ago
Celery chords not working
Categories
(developer.mozilla.org Graveyard :: General, defect)
developer.mozilla.org Graveyard
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: robhudson, Unassigned)
Details
(Keywords: in-triage)
I noticed today that the chord callbacks were not getting called. For example, running `./manage.py reindex -p 2 -c 500` should trigger a pre-task, a group of indexing tasks, then a post-task to finalize the index. I noticed it only ran the pre-task and indexing tasks and the finalize tasks was never run.
I tested that if we swap out the celery result backend to using redis it works.
If the database result backend is not working I'm not sure if we can fix this right now, so I'm filing this bug.
| Reporter | ||
Comment 1•10 years ago
|
||
Grepping the code, the following tasks are affected:
* Reindexing content into Elasticsearch
* Rendering stale documents (to remove the render lock)
* Building the sitemap
| Reporter | ||
Comment 2•10 years ago
|
||
Since this affects more than just search I'm putting it back into the General component.
Component: Search → General
Comment 3•7 years ago
|
||
I don't know what or where this was fixed but it's certainly working fine in master today.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•