lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-3884) smoke tester on cygwin fails when testing example due to tlog recovery
Date Tue, 25 Sep 2012 18:08:08 GMT

     [ https://issues.apache.org/jira/browse/SOLR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man updated SOLR-3884:
---------------------------

    Description: 
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

The crux of the issue seems to be...
* the same directory is reused for testing the example in java6 and then java7
* in some versions of cygwin, SIGINT does not do a clean shutdown of jetty+solr (with jvm
close hooks that would do a hard commit)
* when solr is shutdown uncleanly (the java6 run), the tlog is used on startup of the next
(java7) run.
* tlog recovery concurrent with rapid updates on startup can be problematic, commits may be
ignored.

The underlying questions about dealing with tlog recovery and concurrent updates from external
clients have been spun off into SOLR-3888.  this issue is focusing on changes that should
be considered for the smoke tester.

  was:
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

        Summary: smoke tester on cygwin fails when testing example due to tlog recovery  (was:
possible bug in how commits are handled during "recovery" mode on startup?)

updated issue summary now that tlog questions have been spun off into SOLR-3888.  For 4.0
we should focus on addressing the smoke tester to run the example in a more consistent way
-- ie: not re-use the directory when running the example with diff jvms.  We can always make
the the smoke tester explicitly trigger tlog recoery and smoke test that as a distinct task
(done in both jvms) as part of SOLR-3888
                
> smoke tester on cygwin fails when testing example due to tlog recovery
> ----------------------------------------------------------------------
>
>                 Key: SOLR-3884
>                 URL: https://issues.apache.org/jira/browse/SOLR-3884
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>             Fix For: 4.0
>
>         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.
> https://mail-archives.apache.org/mod_mbox/lucene-dev/201209.mbox/%3C6C78E97C707B5B4C8CC61D44F87545863ED73E@SUEX10-mbx-03.ad.syr.edu%3E
> The crux of the issue seems to be...
> * the same directory is reused for testing the example in java6 and then java7
> * in some versions of cygwin, SIGINT does not do a clean shutdown of jetty+solr (with
jvm close hooks that would do a hard commit)
> * when solr is shutdown uncleanly (the java6 run), the tlog is used on startup of the
next (java7) run.
> * tlog recovery concurrent with rapid updates on startup can be problematic, commits
may be ignored.
> The underlying questions about dealing with tlog recovery and concurrent updates from
external clients have been spun off into SOLR-3888.  this issue is focusing on changes that
should be considered for the smoke tester.

--
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