Likely you should implement a custom MergeScheduler (MergePolicy picks which merges to do, and MergeScheduler schedules them).
Or you could e.g. make a MergePolicy that picks only "easy-ish" merges during busy times and leaves hard merges for later. Just be very careful: if merges fall behind and your index has too many segments then things can be even worse (more open file descriptors, slower searching, more RAM used, etc.). Mike McCandless http://blog.mikemccandless.com On Thu, Jun 12, 2014 at 12:38 AM, Jamie <ja...@mailarchiva.com> wrote: > Hi All, > > What's the best way to control the timing when merges occur? In particular, > I'd like less merges to occur when the rate of indexing new documents is > high, and more merges to occurs when the indexing rate drops. What's the > best way to accomplish this? Do I need to implement a custom merge policy? > > Thank you in advance for your consideration. > > Jamie > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
