vigyasharma commented on issue #13883: URL: https://github.com/apache/lucene/issues/13883#issuecomment-3022310526
> I'd suggest creating a fresh new MergeScheduler that would schedule merges in a shared thread pool for all IndexWriters? Merging activity would be controlled by the size of the thread pool (which is akin to CMS's maxThreadCount) and the max size of the queue (akin to CMS's maxMergeCount-maxThreadCount). So the multi-tenant CMS will schedule/throttle merges across all registered writers, agnostic of which writer they came from? I like the simplicity of this approach. We will still need to maintain a merge -> writer mapping, and cleanly handle index writer close(), but that is not too complex. Would we run the risk of accidentally starving merges from a writer because smaller merges from other writers got preferred? Maybe it's not an issue if merges are small enough.? Also, IIUC, there is a back pressure on indexing if there are too many pending merges. In this setup, would we uniformly throttle all the writers? -- 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
