On 2/7/2015 10:30 AM, Shawn Heisey wrote: > Lastly, CMS itself could be modified to severely throttle the incoming > thread rather than completely stall it. If the throttled rate were high > enough to ensure that the JDBC connection saw activity at least once > every 15 seconds, that would be enough for any sanely configured > database. I'm mentally tossing around an idea for a "maxStallTime" > option instead of actual throttling ... something that would allow the > incoming thread to alternate running and stalling for certain time periods.
Followup: I believe that this section of the javadoc for ConcurrentMergeScheduler is wrong: * <p>If the number of merges exceeds the max number of threads * then the largest merges are paused until one of the smaller * merges completes.</p> If this was how it worked, the dataimport handler would not be having a problem, because the smallest merge would complete in mere seconds, freeing up a slot very quickly, and allowing the incoming thread to continue. The behavior I have seen is that the largest merge is given top priority and all other merges are paused. If CMS can be altered so that the javadoc is correct, I believe the DIH problem I have described would disappear. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
