lucene-dev mailing list archives

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


Steven Rowe commented on SOLR-3884:

I think it might be this:
The author does note that the Java shutdown hook is no longer called though.

In an earlier thread a workaround is given - from []:

Since apparently nobody wants to take ownership of this regression
I'll point out the workaround, for the benefit of those googling
and landing on this thread: start Java with -Xrs and use Ctrl-Break
instead of Ctrl-C. This will disable thread dump and break any
application that relies on normal signal handling, though.

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