Consider time-based MergeScheduler [LUCENE-5135]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Very often search traffic follows the wave pattern, which could mean that more
aggressive merging could be done during periods with lower query
rates (e.g. nights and weekends) ... or maybe during that time more segments could be allowed to live in the index, assuming that after allowing that for some time, the subsequent merge could be bigger/more thorough, so to speak.
See http://search-lucene.com/m/D7ypz1gT2H91
---
Migrated from [LUCENE-5135](https://issues.apache.org/jira/browse/LUCENE-5135) by Otis Gospodnetic (@otisg)
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reading the linked LUCENE-5135 discussion and determine the intended time-based MergeScheduler behavior; the issue has no acceptance criteria defining when the work is done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100