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

Erick Erickson commented on SOLR-8135:
--------------------------------------

This feels a little like a band-aid. If I'm reading this right, the sequence is 
this:

1> the test changes the configs, kicking off reloads for the cores
2> the test deletes the collection

<2> happens before <1> is complete, thus the race as the reload doesn't get 
around to reloading the core after the delete happens and the core is closed. 
Is this about right?

Tim's comment about a delay suggests that if we waited for the config changes 
to complete reloading before continuing the test we'd be OK. It seems like a 
better option would be to have Solr not start the delete while reloads were 
pending. Or more generally not start carrying out one command while another 
potentially conflicting operation was being carried.

Not sure how hard having Solr be smart enough to delay "potentially 
conflicting" operations would be though.


> SolrCloudExampleTest.testLoadDocsIntoGettingStartedCollection reproducible 
> failure
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-8135
>                 URL: https://issues.apache.org/jira/browse/SOLR-8135
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: Trunk
>            Reporter: Hoss Man
>            Assignee: Noble Paul
>         Attachments: SOLR-8135.failure.log, SOLR-8135.patch, SOLR-8135.patch
>
>
> No idea what's going on here, noticed it while testing out an unrelated patch 
> -- seed reproduces against pristine trunk...
> {noformat}
>    [junit4]   2> NOTE: reproduce with: ant test  
> -Dtestcase=SolrCloudExampleTest 
> -Dtests.method=testLoadDocsIntoGettingStartedCollection 
> -Dtests.seed=59EA523FFF6CB60F -Dtests.slow=true -Dtests.locale=es_MX 
> -Dtests.timezone=Africa/Porto-Novo -Dtests.asserts=true 
> -Dtests.file.encoding=ISO-8859-1
>    [junit4] FAILURE 49.5s | 
> SolrCloudExampleTest.testLoadDocsIntoGettingStartedCollection <<<
>    [junit4]    > Throwable #1: java.lang.AssertionError: Delete action failed!
>    [junit4]    >      at 
> __randomizedtesting.SeedInfo.seed([59EA523FFF6CB60F:4A896050CE030FA9]:0)
>    [junit4]    >      at 
> org.apache.solr.cloud.SolrCloudExampleTest.doTestDeleteAction(SolrCloudExampleTest.java:169)
>    [junit4]    >      at 
> org.apache.solr.cloud.SolrCloudExampleTest.testLoadDocsIntoGettingStartedCollection(SolrCloudExampleTest.java:145)
>    [junit4]    >      at 
> org.apache.solr.BaseDistributedSearchTestCase$ShardsRepeatRule$ShardsFixedStatement.callStatement(BaseDistributedSearchTestCase.java:963)
>    [junit4]    >      at 
> org.apache.solr.BaseDistributedSearchTestCase$ShardsRepeatRule$ShardsStatement.evaluate(BaseDistributedSearchTestCase.java:938)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to