[SOLR-3884] smoke tester on cygwin fails when testing example due to tlog recovery

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0, 4.1, 6.0
• Assignee: Steven Rowe
• Reporter: Chris M. Hostetter
• Created: 24/Sep/12 22:53
• Updated: 09/May/16 18:48
• Resolved: 25/Sep/12 19:59

Description

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/[e-mail]%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.

Issue Links

• is related to: SOLR-3888 need beter handling of external add/commit requests during tlog recovery
• is related to: SOLR-3889 SmokeTest fail on my Linux machine.
• relates to: SOLR-3861 Refactor SolrCoreState so that it's managed by SolrCore .