Revise ThreadAffinityDocumentsWriterThreadPool queue handling [LUCENE-3060]
Open
affects-version:4.0-ALPHA
legacy-jira-fix-version:4.9
legacy-jira-fix-version:6.0
legacy-jira-priority:Minor
module:core/index
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Spin-off from #4097... In ThreadAffinityDocumentsWriterThreadPool#getAndLock() we had talked about switching from a per-threadstate queue (safeway model) to a single queue (whole foods)
---
Migrated from [LUCENE-3060](https://issues.apache.org/jira/browse/LUCENE-3060) by Simon Willnauer (@s1monw), updated May 09 2016
Contributor guide
Research direction
Start with ThreadAffinityDocumentsWriterThreadPool#getAndLock() and trace how its per-threadstate queue is handled. Compare that behavior with the proposed single-queue model described in the issue; the issue does not specify tests, files, or acceptance criteria for determining when the change is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, search
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100