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 22:34:07 GMT


Steven Rowe commented on SOLR-3884:

bq. I've noticed that ^C in cygwin no longer works to stop the JVM.

Ctrl-C doesn't stop Cygwin Python for me - running {{}} anyway - but from
cygwin terminal, xterm, and rxvt, Ctrl-C *does* halt Solr started via {{java -jar start.jar}}
from the unpacked binary distribution's {{example/}} directory.

My cygwin version (from {{uname -srv}}):

{noformat}CYGWIN_NT-6.1-WOW64 1.7.16(0.262/5/3) 2012-07-20 22:55{noformat}
> 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