You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
Description
ConcurrentMergeSchedulercomputes max thread counts assuming a singleIndexWriterin the JVM. But it's common with Solr or Elasticsearch to have tens of activeIndexWriters running in the same JVM. Could we makeConcurrentMergeSchedulermore multi-tenant, or introduce a new multi-tenant merge scheduler that accounts for the fact that the JVM is shared across multiple indexes?The text was updated successfully, but these errors were encountered: