lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <>
Subject [jira] [Commented] (SOLR-3884) smoke tester on cygwin fails when testing example due to tlog recovery
Date Tue, 25 Sep 2012 23:54:08 GMT


Jack Krupansky commented on SOLR-3884:

It failed in the Java 1.6 tests for me:

    test solr example w/ Java 6...
      start Solr instance (log=/home/projects/lucene_solr_4_0/smoke-temp/unpack/apache-solr-4.0.0/solr-example.log)...
      startup done
      test utf8...
      index example docs...
      run query...
FAILED: response is:
<?xml version="1.0" encoding="UTF-8"?>
<lst name="responseHeader"><int name="status">0</int><int name="QTime">0</int><lst
name="params"><str name="q">video</str></lst></lst><result name="response"
numFound="0" start="0"></result>

      stop server (SIGINT)...
Traceback (most recent call last):
  File "dev-tools/scripts/", line 1123, in <module>
  File "dev-tools/scripts/", line 1071, in main
  File "dev-tools/scripts/", line 1113, in smokeTest
  File "dev-tools/scripts/", line 424, in unpack
  File "dev-tools/scripts/", line 537, in verifyUnpacked
  File "dev-tools/scripts/", line 612, in testSolrExample
RuntimeError: query on solr example instance failed

> smoke tester on cygwin fails when testing example due to tlog recovery
> ----------------------------------------------------------------------
>                 Key: SOLR-3884
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Steven Rowe
>             Fix For: 4.0, 4.1, 5.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.
> 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:

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

View raw message