You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/03/06 17:18:43 UTC

[jira] [Commented] (SOLR-5628) Cloud test harness can cause index files to be deleted before IndexWriter is closed

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

ASF subversion and git services commented on SOLR-5628:
-------------------------------------------------------

Commit 1574942 from hossman@apache.org in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1574942 ]

SOLR-5628: work arround for this test to avoid whatever bug is in the cloud test framework (merge r1574941)

> Cloud test harness can cause index files to be deleted before IndexWriter is closed
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-5628
>                 URL: https://issues.apache.org/jira/browse/SOLR-5628
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>
> This bug was orriginally opened because Jenkins uncovered a test seed that causes a reproducible IndexWriter assertion failure in TestDistribDocBasedVersion on the 4x branch.
> McCandless helped dig in and believe that something in the way the solr test framework is setup is causing the test to delete the index dirs before the IndexWriter is being closed. Meanwhile, the failures later reproduced in other seeds on both 4x and trunk -- and it appears that recent changes caused the nature of the failure to change, so that now -- in addition to the IndexWriter assertion failure -- the test cleanup also stalls out and the test runner has to terminate some stalled threads.
> One interesting factor about this test is that at the end of the test there were docs that had been added that were not committed -- which is probably unusually for most tests, and may explain why more cloud tests aren't exhibiting similar symptoms more often.
> *When a useless (from perspective of what the test is trying to verify) "commit" was added to the test, the failing seed stoped reproducing.*
> An example of how to reliably reproduce this problem on an (older version of) trunk...
> {noformat}
> svn update -r 1574381 && ant clean && cd solr/core && ant test  -Dtestcase=TestDistribDocBasedVersion -Dtests.seed=1249227945045A2E -Dtests.slow=true -Dtests.locale=ko_KR -Dtests.timezone=America/Monterrey -Dtests.file.encoding=ISO-8859-1
> {noformat}
> Original email thread...
> https://mail-archives.apache.org/mod_mbox/lucene-dev/201401.mbox/%3Calpine.DEB.2.02.1401100930260.20275@frisbee%3E



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org