Description

ConcurrentMergeScheduler computes max thread counts assuming a single IndexWriter in the JVM. But it's common with Solr or Elasticsearch to have tens of active IndexWriters running in the same JVM. Could we make ConcurrentMergeScheduler more multi-tenant, or introduce a new multi-tenant merge scheduler that accounts for the fact that the JVM is shared across multiple indexes?