Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 26 Sep 2012 09:34:07 +1100 (NCT)
From: "Steven Rowe (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <1095840317.125542.1348612447889.JavaMail.jiratomcat@arcas>
In-Reply-To: <140538595.119327.1348527247971.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (SOLR-3884) smoke tester on cygwin fails when
 testing example due to tlog recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463292#comment-13463292 ] 

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 {{smokeTestRelease.py}} 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: https://issues.apache.org/jira/browse/SOLR-3884
>             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.
> 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