Re: [I] A multi-tenant ConcurrentMergeScheduler [lucene]

2025-06-17 Thread via GitHub
vigyasharma commented on issue #13883: URL: https://github.com/apache/lucene/issues/13883#issuecomment-2982081708 Thanks @yaser-aj , happy to see progress on this project. You're on the right track with understanding the problem. We want CMS to be aware of merge demands across IndexWr

Re: [I] A multi-tenant ConcurrentMergeScheduler [lucene]

2025-06-16 Thread via GitHub
yaser-aj commented on issue #13883: URL: https://github.com/apache/lucene/issues/13883#issuecomment-2978379030 Me, @lukewilner, @atharvkashyap, and @N624-debu are students from Carnegie Mellon University, and we’ll be working on this issue as part of a mentored summer course focused on coll

[I] A multi-tenant ConcurrentMergeScheduler [lucene]

2024-10-10 Thread via GitHub
jpountz opened a new issue, #13883: URL: https://github.com/apache/lucene/issues/13883 ### 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 `IndexWriter`s ru