[ https://issues.apache.org/jira/browse/SOLR-9671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15600279#comment-15600279 ]
Mikhail Khludnev commented on SOLR-9671: ---------------------------------------- I still can't catch it. I added a delay into {{CoreContainer.create(CoreDescriptor, boolean)}} right after {{ zkSys.getZkController().preRegister(dcore);}} for one core (testcollection_shard2_replica2). I've got bq. PeerSync PeerSync: core=testcollection_shard2_replica1 url=http://127.0.0.1:52001/solr START replicas=[http://127.0.0.1:52182/solr/testcollection_shard2_replica2/] nUpdates=100 bq. o.a.s.c.ShardLeaderElectionContext I am the new leader: http://127.0.0.1:52001/solr/testcollection_shard2_replica1/ shard2 however between these lines we see a protection from infinite remote calls: bq. ERROR (qtp2143243594-237) [n:127.0.0.1:52182_solr ] o.a.s.s.HttpSolrCall got /testcollection_shard2_replica2/get=> null but this didn't happen at the failed job. hmm.... > TestMiniSolrCloudCluster blowup jvm with remote /get requests > ------------------------------------------------------------- > > Key: SOLR-9671 > URL: https://issues.apache.org/jira/browse/SOLR-9671 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Mikhail Khludnev > Labels: cloud > Attachments: > TestMiniSolrCloudCluster-testCollectionCreateSearchDelete-fail-brief.txt, > TestMiniSolrCloudCluster-testCollectionCreateSearchDelete-fail.zip > > > this is epic https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/1994/ > There is no many cores, I checked. It seems like cluster blow up when tries > to launch after collection remove. Haven't tried to reproduce it locally -- 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