lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-3884) possible bug in how commits are handled during "recovery" mode on startup?
Date Tue, 25 Sep 2012 17:38:08 GMT


Hoss Man commented on SOLR-3884:

Doing a "kill -2" on the java process from a different window seems to immediately abort the
JVM (no graceful shutdown that does a commit).
The latter may be happening with the python script too?

That could explain how a tlog would be left in the directory after calling the testSolrExample()
method, but it still leaves some open questions...

1) according to sarowe, he's seeing this problem (and his smoke test logs show tlog recovery)
even when using a pristine copy of the "unpack" dir - so why is there a tlog in that case?

2) how should tlog recovery be "fixed" to better handle this situation (ie: docs & commits
coming in during recovery) in a real world situation.
> possible bug in how commits are handled during "recovery" mode on startup?
> --------------------------------------------------------------------------
>                 Key: SOLR-3884
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>         Attachments: java6.solr-example.log, java7.solr-example.log, solr-example.log
> while testing out 4.0-rc0, sarowe noted the he was seeing the smoke tester script fail
while sanity checking the solr example.
> I'm not certain, but looking at his logs, i think this suggests a bug in how commits
are handled when a newly started server is in "recovery" mode

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

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

View raw message