django-haystack / django-haystack/celery-haystack
Is celery-haystack not honoring prefetch settings?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 226
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
We've noticed that celery-haystack is sucking down all messages in the queue, despite explicitly setting these variables:
export CELERYD_PREFETCH_MULTIPLIER=1
export CELERY_ACKS_LATE=True
Using -Ofair while starting the workers...
We are using:
celery==3.1.25
celery-haystack==0.10
Django==1.8.4
I don't understand why this is specific to celery-haystack, but as far as I can tell, it is.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing the queue behavior with celery==3.1.25, celery-haystack==0.10, and Django==1.8.4 using the listed prefetch and acknowledgment settings. Done means determining whether celery-haystack causes the settings to be ignored and identifying a verified fix or clear explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100