right. We've got the autoHard commit configured only atm. The soft-commits are controlled on the client. It was just easier to implement the first version of our internal commit policy that will commit to all solr instances at once. This is where we have noticed the reported behavior.
On Wed, Oct 2, 2013 at 9:32 AM, Bram Van Dam <bram.van...@intix.eu> wrote: > if there are no modifications to an index and a softCommit or hardCommit >>>> issued, then solr flushes the cache. >>>> >>> > Indeed. The easiest way to work around this is by disabling auto commits > and only commit when you have to. >
