[LUCENE-2063] Use thread pool in ConcurrentMergeScheduler

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.9.1
• Fix Version/s: 4.0-ALPHA
• Component/s: core/index
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Jason Rutherglen
• Created: 13/Nov/09 19:10
• Updated: 28/Aug/22 12:14
• Resolved: 24/Jan/11 21:12

Description

Currently it looks like CMS creates a new thread object for each
merge, which may not be expensive anymore on Java5+ JVMs,
however we can fairly simply implement the Java5 thread pooling.
Also I'm thinking we may be interested in using thread pools for
other tasks in IndexWriter (such as LUCENE-2047 performing
deletes in the background).