If you set maxWarmingSearchers to 1 then you cannot issue an overlapping commit. Slaves won't poll for a new index version while replication is in progress.
It works well in my environment where there is a high update/commit frequency, about a thousand documents per minute. The system even behaves well a thousand updates per second and a commit per minute with a poll interval of 2 seconds. On Thursday 17 February 2011 11:54:32 dan sutton wrote: > Hi, > > Keeping the thread alive, any thought on only doing replication if > there is no warming currently going on? > > Cheers, > Dan > > On Thu, Feb 10, 2011 at 11:09 AM, dan sutton <danbsut...@gmail.com> wrote: > > Hi, > > > > If the replication window is too small to allow a new searcher to warm > > and close the current searcher before the new one needs to be in > > place, then the slaves continuously has a high load, and potentially > > an OOM error. we've noticed this in our environment where we have > > several facets on large multivalued fields. > > > > I was wondering what the list though about modifying the replication > > process to skip polls (though warning to logs) when there is a > > searcher in the process of warming? Else as in our case it brings the > > slave to it's knees, workaround was to extend the poll interval, > > though not ideal. > > > > Cheers, > > Dan -- Markus Jelsma - CTO - Openindex http://www.linkedin.com/in/markus17 050-8536620 / 06-50258350
