[
https://issues.apache.org/jira/browse/SOLR-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834238#comment-15834238
]
Alan Woodward commented on SOLR-9869:
-------------------------------------
I got a test failure when running this locally:
{code}
[10:20:04.308] ERROR 8.38s J0 | TestMiniSolrCloudCluster.testStopAllStartAll
<<<
> Throwable #1: java.lang.ArrayIndexOutOfBoundsException: 4
> at
__randomizedtesting.SeedInfo.seed([3F4B441AB7975037:49755B69F6A0FD18]:0)
> at
java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:387)
> at
java.util.concurrent.CopyOnWriteArrayList.get(CopyOnWriteArrayList.java:396)
> at java.util.Collections$UnmodifiableList.get(Collections.java:1309)
> at
org.apache.solr.cloud.TestMiniSolrCloudCluster.testStopAllStartAll(TestMiniSolrCloudCluster.java:345)
{code}
So it looks as though we still need to deal with concurrent removals?
> MiniSolrCloudCluster does not always remove jettys from running list after
> stopping them
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-9869
> URL: https://issues.apache.org/jira/browse/SOLR-9869
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Tests
> Reporter: Mike Drob
> Assignee: Alan Woodward
> Attachments: SOLR-9869.patch, SOLR-9869.patch
>
>
> MiniSolrCloudCluster has two {{stopJettySolrRunner}} methods that behave
> differently.
> The {{int}} version calls {{jettys.remove(index);}} to remove the now stopped
> jetty from the list of running jettys.
> The version that takes a {{JettySolrRunner}}, however, does not modify the
> running list.
> This can cause calls to {{getReplicaJetty}} to fail after a call to {{stop}}
> because we will try to get the base url of a stopped jetty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
