[
https://issues.apache.org/jira/browse/SOLR-9671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-9671:
-----------------------------------
Attachment: TestMiniSolrCloudCluster-epic-fail.zip
when TestMiniSolrCloudCluster.testCollectionCreateSearchDelete() tries to
create collection last time. we have wait loop
bq. (qtp1915946497-3004) [ ] o.a.s.h.a.CoreAdminOperation Checking request
status for : a4310491-abb0-4d8d-a290-2f8d2a909be7241809864829983
and
bq.(parallelCoreAdminExecutor-1329-thread-1) [ ] o.a.s.u.PeerSync PeerSync:
core=testcollection_shard2_replica2 url=http://127.0.0.1:42320/solr DONE. We
have no versions. sync failed.
and then it just
bq. java.lang.OutOfMemoryError: Java heap space
Do you have any clues to troubleshoot?
> 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-epic-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: [email protected]
For additional commands, e-mail: [email protected]
