[
https://issues.apache.org/jira/browse/SOLR-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358149#comment-14358149
]
Damien Kamerman commented on SOLR-7191:
---------------------------------------
With 10K cores I was still seeing many cores stuck in recovery.
I reduced CoreContainer.load() coreLoadExector to be 24 (cfg.coreLoadThreads)
threads (from max int); I guess I'm now assuming replicas to be on other nodes.
I reduced ZkContainer.coreZkRegister to be 24 threads (from max int) and added
a sort to SolrCore.getCores(). The sort ensures replicas are available.
I tested with solr 4.10.4; 2 x nodes; 5K collections; 10K cores. All green in
19min.
Please review patch.
Would still like to see SOLR-6399 and a SolrCloud LotsOfCores as per Erick.
> Improve stability and startup performance of SolrCloud with thousands of
> collections
> ------------------------------------------------------------------------------------
>
> Key: SOLR-7191
> URL: https://issues.apache.org/jira/browse/SOLR-7191
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.0
> Reporter: Shawn Heisey
> Labels: performance, scalability
> Attachments: lots-of-zkstatereader-updates-branch_5x.log
>
>
> A user on the mailing list with thousands of collections (5000 on 4.10.3,
> 4000 on 5.0) is having severe problems with getting Solr to restart.
> I tried as hard as I could to duplicate the user setup, but I ran into many
> problems myself even before I was able to get 4000 collections created on a
> 5.0 example cloud setup. Restarting Solr takes a very long time, and it is
> not very stable once it's up and running.
> This kind of setup is very much pushing the envelope on SolrCloud performance
> and scalability. It doesn't help that I'm running both Solr nodes on one
> machine (I started with 'bin/solr -e cloud') and that ZK is embedded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
