[
https://issues.apache.org/jira/browse/SOLR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463100#comment-13463100
]
Steven Rowe commented on SOLR-3884:
-----------------------------------
{quote}
I think it might be this: http://cygwin.com/ml/cygwin/2012-07/msg00250.html
The author does note that the Java shutdown hook is no longer called though.
{quote}
In an earlier thread a workaround is given - from
[http://cygwin.com/ml/cygwin/2012-05/msg00482.html]:
{quote}
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.
{quote}
> 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
> 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.
> https://mail-archives.apache.org/mod_mbox/lucene-dev/201209.mbox/%3c6c78e97c707b5b4c8cc61d44f87545863ed...@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: [email protected]
For additional commands, e-mail: [email protected]
