I'm also hitting some threading issues with autocommit -- JConsole
does not show deadlock, but it shows some threads 'BLOCKED' on
scheduleCommitWithin
Perhaps this has something to do with the changes we made for: SOLR-793
I am able to fix this (at least I don't see the blocking with the dat
On 18-Nov-08, at 12:18 PM, Mark Miller wrote:
Mike Klaas wrote:
autoCommitCount is written in a CommitTracker.synchronized block
only. It is read to print stats in an unsynchronized fashion,
which perhaps could be fixed, though I can't see how it could cause
a problem
lastAddedTime i
On 18 Nov 2008, at 20:18, Mark Miller wrote:
Mike Klaas wrote:
autoCommitCount is written in a CommitTracker.synchronized block
only. It is read to print stats in an unsynchronized fashion,
which perhaps could be fixed, though I can't see how it could cause
a problem
lastAddedTime is
Mike Klaas wrote:
autoCommitCount is written in a CommitTracker.synchronized block
only. It is read to print stats in an unsynchronized fashion, which
perhaps could be fixed, though I can't see how it could cause a problem
lastAddedTime is only written in a call path within a
DirectUpdate
On 18-Nov-08, at 8:54 AM, Mark Miller wrote:
Mark Miller wrote:
Toby Cole wrote:
Has anyone else experienced a deadlock when the
DirectUpdateHandler2 does an autocommit?
I'm using a recent snapshot from hudson (apache-
solr-2008-11-12_08-06-21), and quite often when I'm loading data
the s
Mark Miller wrote:
Toby Cole wrote:
Has anyone else experienced a deadlock when the DirectUpdateHandler2
does an autocommit?
I'm using a recent snapshot from hudson
(apache-solr-2008-11-12_08-06-21), and quite often when I'm loading
data the server (tomcat 6) gets stuck at line 469 of
DirectU
Toby Cole wrote:
Has anyone else experienced a deadlock when the DirectUpdateHandler2
does an autocommit?
I'm using a recent snapshot from hudson
(apache-solr-2008-11-12_08-06-21), and quite often when I'm loading
data the server (tomcat 6) gets stuck at line 469 of
DirectUpdateHandler2:
