[ https://issues.apache.org/jira/browse/SOLR-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129334#comment-15129334 ]
Timothy Potter commented on SOLR-8135: -------------------------------------- I can fix the test to wait longer after it issues a config change but that will mask a race condition that the SolrConfigHandler refreshconf thread attempts to refresh a core that is being shutdown down. {code} [junit4] 2> 42606 INFO (qtp1036148039-29) [n:127.0.0.1:58528_ ] o.a.s.c.SolrCore [gettingstarted_shard1_replica1] CLOSING SolrCore org.apache.solr.core.SolrCore@53fda895 {code} and then later in the log, you have: {code} [junit4] 2> 42629 INFO (SolrConfigHandler-refreshconf) [n:127.0.0.1:58528_ c:gettingstarted s:shard1 r:core_node4 x:gettingstarted_shard1_replica1] o.a.s.c.ConfigSetProperties Did not find ConfigSet properties, assuming default properties: Can't find resource 'configsetprops.json' in classpath or '/configs/gettingstarted', cwd=/home/hossman/lucene/dev/solr/build/solr-core/test/J0 [junit4] 2> 42629 INFO (SolrConfigHandler-refreshconf) [n:127.0.0.1:58528_ c:gettingstarted s:shard1 r:core_node4 x:gettingstarted_shard1_replica1] o.a.s.c.CoreContainer Reloading SolrCore 'gettingstarted_shard1_replica1' using configuration from collection gettingstarted [junit4] 2> 42630 ERROR (SolrConfigHandler-refreshconf) [n:127.0.0.1:58528_ c:gettingstarted s:shard1 r:core_node4 x:gettingstarted_shard1_replica1] o.a.s.h.SolrConfigHandler Unable to refresh conf [junit4] 2> org.apache.solr.common.SolrException: Unable to reload core [gettingstarted_shard1_replica1] [junit4] 2> at org.apache.solr.core.CoreContainer.reload(CoreContainer.java:837) [junit4] 2> at org.apache.solr.core.SolrCore$11.run(SolrCore.java:2602) [junit4] 2> at org.apache.solr.handler.SolrConfigHandler$Command$1.run(SolrConfigHandler.java:212) {code} I see some checks for whether the core is closed, so maybe there's nothing we can do better to detect this race condition, but would appreciate if [~noble.paul] could take a closer look at the checks? If not, the only fix here is to wait longer for the config changes to take effect before issuing the delete. > 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 > Attachments: SOLR-8135.failure.log, 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