django-haystack / django-haystack/django-haystack
rebuild_index worker issue
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 1.3k
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 3
Description
python manage.py rebuild_index -k 6 , is only indexing the 1st worker , the result is not combined .
for example i have a table with 1000 records , when i run with 6 workers i am getting only count of 40 to 150 records... strange behaviour
Contributor guide
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
Start by reproducing the issue with python manage.py rebuild_index -k 6 using a dataset of about 1,000 records, then trace the rebuild_index worker entry point and how worker results are combined. Done means the indexed count includes records from all six workers rather than only the first worker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100