[ https://issues.apache.org/jira/browse/SOLR-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803676#comment-13803676 ]
Mark Miller commented on SOLR-5381: ----------------------------------- bq. The only instance when a node needs to know about the state of other shards is when it needs to forward a request. It would like to know the state of the other shards as it often has to query against all the shards in a collection and we don't want to keep hitting a shard that is down and we don't want to take forever to hit a shard that just came up ... bq. That information can be looked up on demand and cached. I don't think I'm sold on that yet. Perhaps you need to do stuff like that for truly massive clusters, but until we proof point everything on a few thousand nodes, it doesn't seem worth this kind of change to me. bq. Nobody should need to watch other shards on a realtime basis. I I do think it's important that we continue to propagate cluster state changes relatively quickly after they happen. > Split Clusterstate and scale > ----------------------------- > > Key: SOLR-5381 > URL: https://issues.apache.org/jira/browse/SOLR-5381 > Project: Solr > Issue Type: Improvement > Components: SolrCloud > Reporter: Noble Paul > Assignee: Noble Paul > Original Estimate: 2,016h > Remaining Estimate: 2,016h > > clusterstate.json is a single point of contention for all components in > SolrCloud. It would be hard to scale SolrCloud beyond a few thousand nodes > because there are too many updates and too many nodes need to be notified of > the changes. As the no:of nodes go up the size of clusterstate.json keeps > going up and it will soon exceed the limit impossed by ZK. > The first step is to store the shards information in separate nodes and each > node can just listen to the shard node it belongs to. We may also need to > split each collection into its own node and the clusterstate.json just > holding the names of the collections . > This is an umbrella issue -- This message was sent by Atlassian JIRA (v6.1#6144) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org