jpountz commented on issue #13883: URL: https://github.com/apache/lucene/issues/13883#issuecomment-3022942485
I have similar questions, but I think we can figure them out? We have options like running merges in the indexing thread (a la SerialMergeScheduler) when that would help. IMO this approach potentially gives other benefits, e.g. imagine that the multi-tenant merge scheduler could be provided with the same thread pool that is used for indexing. This would give better control over the overall resources used by indexing, vs. today where applications like Solr/Elasticsearc/OpenSearch use a fixed thread pool for indexing but then CMS can create many threads on top of that, wouldn't it be much better if one could easily use the same thread pool across indexing, flushing and merging? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
