[
https://issues.apache.org/jira/browse/SOLR-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348836#comment-14348836
]
Shawn Heisey commented on SOLR-7191:
------------------------------------
As I said above, I started over with a fresh cloud example because of the
problems I was having. Late last night, the creation of 4000 collections
completed.
This morning, I went to the admin UI page which I still had open, and did a
shift-refresh on the main page. Somehow, pulling the list of cores for the
dropdown (there are 4001 of them) sent Solr into a tailspin where all the
shards were marked down (orange) on the cloud graph, then they started coming
back up. Half an hour after this event started, only about 150 out of the 4000
collections had fully recovered. That projects full recovery to take half the
day ... and this is just from basically opening the admin UI to the dashboard!
For situations where large numbers of cluster bits must change state, could
there be an improvement made in the overseer queue messages to change the state
of multiple bits? If we could have a single message change the state of up to
1000 at once (and perhaps have a special code to indicate all of the replicas
on a node), that would go a long way towards keeping the queue tidy when there
are major events. (I wrote this paragraph before seeing Shalin's note about
optimizing the node shutdown case)
[~shalinmangar], I will try again with branch_5x.
> 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
>
> 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]
