[
https://issues.apache.org/jira/browse/SOLR-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285925#comment-14285925
]
Jessica Cheng Mallet commented on SOLR-6521:
--------------------------------------------
The patch is locking the entire cache for all loading, which might not be an
ideal solution for a cluster with many, many collections. Guava's
implementation of LocalCache would only lock and wait on "Segment"s, which
increases the concurrency level (which is tunable).
> CloudSolrServer 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
>
>
> 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]
