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

Steven Rowe commented on SOLR-3884:
-----------------------------------

Although under Cygwin Ctrl-C halts java programs for me, the shutdown hook 
isn't invoked, e.g.:

{code:java}
public class ShutdownHookTest {
  public static void main(String args[]) {
    Runtime.getRuntime().addShutdownHook(new Thread() {
      public void run() {
        System.err.println("Hook invoked.");
      }
    });
    while (true) {}
  }
}
{code}

When I run the above and hit Ctrl-C from Cygwin I don't see anything printed to 
the console.  So this is consistent with the behavior Yonik saw with {{kill 
-2}} from another window.

By contrast, from a cmd terminal window, the message does get printed to the 
console.
                
> 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/%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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to