[
https://issues.apache.org/jira/browse/SOLR-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120256#comment-13120256
]
Mark Miller commented on SOLR-2799:
-----------------------------------
The tricky part is that if we ever want to have properties you can update per
shard without removing/adding the whole shard node + info, things get very
tricky. Worth the tradeoff for now though - we need to be able to scale the
huge number of shards.
> SolrCloud reads its entire state from Zookeeper on every update instead of
> what has changed
> -------------------------------------------------------------------------------------------
>
> Key: SOLR-2799
> URL: https://issues.apache.org/jira/browse/SOLR-2799
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Jamie Johnson
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-2799.patch, cloudstate.patch, cloudstate.patch
>
>
> Currently solrcloud reads the entire cloud state from ZK anytime an update is
> scheduled which can be very inefficient with a large number of shards.
> see discussion on user list:
> http://www.lucidimagination.com/search/document/54fa402cf3171bc3/solr_cloud_number_of_shard_limitation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
