lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Krüger <>
Subject Re: Is Overlapping onDeckSearchers=2 really a problem?
Date Thu, 27 Jun 2013 11:59:14 GMT

On Thu, Jun 27, 2013 at 12:23 PM, Robert Krüger <> wrote:
> Hi,
> I have a desktop application where I am "abusing" solr as an embedded
> database accessing it and I am quite happy with everything.
> Performance is more than goog enough for my use case and Solr's query
> capabilities match the requirements of my app quite well. However, I
> have the well-known performance warnings (see subject) in the log
> whenever I index a lot of documents, although I never experience any
> performance problems (might be hidden, though). The properties of my
> app are:
> - I (soft-)commit after every indexed item because I need the changes
> to be visible immediately
> - The commits are serialized
> - I do not have any warming queries configured
> I have read the FAQ but don't see anthing that helps in my case. As I
> said, I am happy with everything as it is but the warning makes me a
> bit nervous (and maybe at some point my customers when their logs are
> full of those warnings). What could I do to eliminate it? Can I
> configure only one searcher to be used or anything like that?
> Thanks for any hints,
> Robert

sometime forcing oneself to describe a problem is the first step to a
solution. I just realized that I also had an autocommit statement in
my config with the exact same amount of time the seemed to be between
the warnings.

I removed that, because I don't think I really need it, and now the
warnings are gone. So it seems it happened whenever my manual commits
overlapped with an autocommit, which, of course, was more likely when
many commits were issued in sequence.

View raw message