[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14050698#comment-14050698
]
Shalin Shekhar Mangar commented on SOLR-5473:
---------------------------------------------
bq. I think because you are trying to tie that issue into this collections
scaling issue, you are okay saying that, oh it just has to be ugly and hackey,
because it's this whole pile of issues we are solving. I don't think it does
have to be ugly or hackey and I think if we let that stay in trunk, it will
haunt us like a lot of other code we have sometimes let in too easily.
bq. Finally, splitting the clusterstate by collection has not been a
contentious issue. Some of the other things you are doing around watchers and
caching is more contentious. We don't have full agreement on them, we never
have, and it really feels like they are coming in as extra pork on a bill with
the JIRA title "make one state.json per collection".
As Noble explained earlier, there's really no point in splitting cluster state
by collection if we were not trying to scale to a large number of collections.
They are the same issue. We aren't doing this because we want to work around ZK
size limits for clusterstate.json. We are trying to make large clusters
possible which have thousands of collections. There is really no point in
splitting the cluster state per collection and multiplying the number of
watchers in the system by the number of collections. Even if ZK and SolrCloud
scales to that limit and I don't know if it would, it is just wasteful and not
required at all.
> Make one state.json per collection
> ----------------------------------
>
> Key: SOLR-5473
> URL: https://issues.apache.org/jira/browse/SOLR-5473
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 5.0
>
> Attachments: SOLR-5473-74 .patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-configname-fix.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473_undo.patch,
> ec2-23-20-119-52_solr.log, ec2-50-16-38-73_solr.log
>
>
> As defined in the parent issue, store the states of each collection under
> /collections/collectionname/state.json node
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
