lukewilner commented on issue #13883: URL: https://github.com/apache/lucene/issues/13883#issuecomment-3016833540
We're currently exploring two possible designs for implementing multi-tenant coordination of merge threads across multiple IndexWriter instances in the same JVM. One option is to introduce a singleton MultiTenantCMSManager that centrally tracks all active ConcurrentMergeScheduler instances and dynamically assigns merge thread budgets based on activity. This approach allows each CMS to remain mostly unchanged, delegating coordination to the manager. The second option is to re-architect the ConcurrentMergeScheduler itself to be fully multi-tenant — managing all IndexWriters and merges internally. We'd appreciate guidance on which direction better aligns with Lucene's architecture and long-term maintainability goals. In the meantime, we will be starting on the first option… -- 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
