[
https://issues.apache.org/jira/browse/SOLR-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reopened SOLR-6521:
-----------------------------------------
There's a test failure on jenkins due to this fix. I guess it's because of:
{code}
locks.get(collection.hashCode() % locks.size())
{code}
http://jenkins.thetaphi.de/job/Lucene-Solr-5.0-Linux/29/
{code}
1 tests failed.
FAILED: org.apache.solr.cloud.HttpPartitionTest.testDistribSearch
Error Message:
-2
Stack Trace:
java.lang.ArrayIndexOutOfBoundsException: -2
at
__randomizedtesting.SeedInfo.seed([117EBA4326468C3C:9098345B5119EC00]:0)
at java.util.ArrayList.elementData(ArrayList.java:418)
at java.util.ArrayList.get(ArrayList.java:431)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.getDocCollection(CloudSolrClient.java:1099)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:762)
at
org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:737)
at
org.apache.solr.cloud.HttpPartitionTest.sendDoc(HttpPartitionTest.java:481)
at
org.apache.solr.cloud.HttpPartitionTest.testRf3(HttpPartitionTest.java:271)
at
org.apache.solr.cloud.HttpPartitionTest.doTest(HttpPartitionTest.java:120)
at
org.apache.solr.BaseDistributedSearchTestCase.testDistribSearch(BaseDistributedSearchTestCase.java:878)
at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
{code}
> CloudSolrClient should synchronize cache cluster state loading
> --------------------------------------------------------------
>
> Key: SOLR-6521
> URL: https://issues.apache.org/jira/browse/SOLR-6521
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Jessica Cheng Mallet
> Assignee: Noble Paul
> Priority: Critical
> Labels: SolrCloud
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6521.patch, SOLR-6521.patch
>
>
> Under heavy load-testing with the new solrj client that caches the cluster
> state instead of setting a watcher, I started seeing lots of zk connection
> loss on the client-side when refreshing the CloudSolrServer
> collectionStateCache, and this was causing crazy client-side 99.9% latency
> (~15 sec). I swapped the cache out with guava's LoadingCache (which does
> locking to ensure only one thread loads the content under one key while the
> other threads that want the same key wait) and the connection loss went away
> and the 99.9% latency also went down to just about 1 sec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
