lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2861) transaction log / realtime-get failures
Date Tue, 01 Nov 2011 16:23:33 GMT


Yonik Seeley commented on SOLR-2861:

bq.  as I said - we can not rely on the order these logs are printed

I think we can rely on that order, and have seen nothing to indicate otherwise.

bq. #those two happen at the same time roughly

Right, hence my comment "The update to id:98 may or may not be in the resulting reader above"
But then after the *next* openIfChanged() should definitely reflect the update.

bq. this doesn't seem like a bug in lucene no?

It absolutely looks like a lucene bug.
But given that it seems to only happen with a mix of hard and soft commits, it should be easier
to track down.  First guess: maybe DirectoryReader.applyDeletes is false when it should be
> transaction log / realtime-get failures 
> ----------------------------------------
>                 Key: SOLR-2861
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>         Attachments:, fail11.xml, fail13_postfix.xml,
fail4.xml, fail5.xml, jenkins_output.txt, solr_debug.patch, trunk-0.txt
> realtime-get or the transaction log fails sometimes

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message