lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3884) possible bug in how commits are handled during "recovery" mode on startup?
Date Tue, 25 Sep 2012 00:40:07 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462300#comment-13462300
] 

Yonik Seeley commented on SOLR-3884:
------------------------------------

Hmmm, just did as simple manual test, and I see evidence of a final commit.
I started a clean stock server, executed "post.sh *xml" (after commenting out the commit command
in the script), then pressed ^C immediately after the docs are added (before any autocommit
could kick in.).

Last lines on the console:
{code}
INFO: [collection1] webapp=/solr path=/update params={} {add=[EN7800GTX/2DHTV/256M (1414039066694909952),
100-435805 (1414039066700152832)]} 0 10
^C2012-09-24 20:25:44.817:INFO:oejs.Server:Graceful shutdown SocketConnector@0.0.0.0:8983
2012-09-24 20:25:44.817:INFO:oejs.Server:Graceful shutdown o.e.j.w.WebAppContext{/solr,file:/opt/code/lusolr/solr/example/solr-webapp/webapp/},/opt/code/lusolr/solr/example/webapps/solr.war
2012-09-24 20:25:45.887:INFO:oejsh.ContextHandler:stopped o.e.j.w.WebAppContext{/solr,file:/opt/code/lusolr/solr/example/solr-webapp/webapp/},/opt/code/lusolr/solr/example/webapps/solr.war
{code}

The only tlog was "capped" (an indicator that everything in the log was subjected to a hard
commit, hence there should be no need to tlog recovery on restart).
{code}

/opt/code/lusolr/solr/example/solr/collection1/data/tlog$ tail -n1 tlog.0000000000000000000

0??D`-SOLR_TLOG_END/opt/code/lusolr/solr/example/solr/collection1/data/tlog$ 
{code}

Starting the server again showed no indication of a tlog replay/recovery.
So I guess this is something more esoteric related to SOLR-3861 that I don't understand yet
(and doesn't happen all the time).

bq.  autocommit during shutdown

FYI, the final commit should be done regardless of any autocommits being enabled, so I assume
you're just referring to that commit, and not a real autocommit triggered by time or number
of documents that happens to coincide with shutdown.

                
> possible bug in how commits are handled during "recovery" mode on startup?
> --------------------------------------------------------------------------
>
>                 Key: SOLR-3884
>                 URL: https://issues.apache.org/jira/browse/SOLR-3884
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>
> while testing out 4.0-rc0, sarowe noted the he was seeing the smoke tester script fail
while sanity checking the solr example.
> https://mail-archives.apache.org/mod_mbox/lucene-dev/201209.mbox/%3C6C78E97C707B5B4C8CC61D44F87545863ED73E@SUEX10-mbx-03.ad.syr.edu%3E
> 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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message