I think the proposal involved using a ThreadPoolExecutor, which seemed to not quite work as well as what we have. I think it'll be easier to simply pass a global context that keeps a counter of the actively running threads, and pass that into each IW's CMS?
On Thu, Apr 14, 2011 at 8:25 AM, Simon Willnauer <[email protected]> wrote: > On Thu, Apr 14, 2011 at 5:20 PM, Jason Rutherglen > <[email protected]> wrote: >> Today the ConcurrentMergeScheduler allows setting the max thread >> count and is bound to a single IndexWriter. >> >> However in the [common] case of multiple IndexWriters running in >> the same process, this disallows one from managing the aggregate >> number of merge threads executing at any given time. >> >> I think this can be fixed, shall I open an issue? > > go ahead! I think I have seen this suggestion somewhere maybe you need > to see if there is one already > > simon >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
