On 4/20/07, Michael Thessel <[EMAIL PROTECTED]> wrote:
The timed commits don't work for me. The webinterface says 0 commits
since the server was restarted. And nothing in the logs as well.
I use:
apache-solr-1.1.0-incubating
Sorry about that--I see that that change was added a few weeks after
Michael Thessel wrote:
Mike Klaas wrote:
On 4/20/07, Michael Thessel <[EMAIL PROTECTED]> wrote:
Hey Erik,
thanks for the fast reply. Yes this could be possible. I currently got
solr running for the indexing of a forum with 100k users. It could
definitely be possible that two commits overlap. B
Mike Klaas wrote:
On 4/20/07, Michael Thessel <[EMAIL PROTECTED]> wrote:
Hey Erik,
thanks for the fast reply. Yes this could be possible. I currently got
solr running for the indexing of a forum with 100k users. It could
definitely be possible that two commits overlap. But I need to commit
all
On 4/20/07, Michael Thessel <[EMAIL PROTECTED]> wrote:
Hey Erik,
thanks for the fast reply. Yes this could be possible. I currently got
solr running for the indexing of a forum with 100k users. It could
definitely be possible that two commits overlap. But I need to commit
all changes because the
Hey Erik,
thanks for the fast reply. Yes this could be possible. I currently got
solr running for the indexing of a forum with 100k users. It could
definitely be possible that two commits overlap. But I need to commit
all changes because the new posts must be available in the search as
soon a
On Apr 19, 2007, at 7:47 PM, Michael Thessel wrote:
in my logs I get from time to time this message:
INFO: PERFORMANCE WARNING: Overlapping onDeckSearchers=2
What does this mean? What can I do to avoid this?
I think you have issued multiple commits (or optimizes) that hadn't
fully finished
Hello,
in my logs I get from time to time this message:
INFO: PERFORMANCE WARNING: Overlapping onDeckSearchers=2
What does this mean? What can I do to avoid this?
Cheers,
Michael
