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
DirectUpdateHandler2:
// Check if there is a commit already scheduled for longer then
this time
if( pending != null &&
pending.getDelay(TimeUnit.MILLISECONDS) >= commitMaxTime )
Anyone got any enlightening tips?
Cheers,
Toby Cole
Software Engineer
Semantico
Lees House, Floor 1, 21-23 Dyke Road, Brighton BN1 3FE
T: +44 (0)1273 358 238
F: +44 (0)1273 723 232
E: [EMAIL PROTECTED]
W: www.semantico.com
There is some inconsistent synchronization I think. Especially
involving pending. Yuck <g>
I would say there are problems with pending, autoCommitCount, and
lastAddedTime. That alone could probably cause a deadlock (who knows),
but it also seems somewhat possible that there is an issue with the
heavy intermingling of locks (there a bunch of locks to be had in that
class). I havn't looked for evidence of that though - prob makes sense
to fix those 3 guys and see if you get reports from there.
