[
https://issues.apache.org/jira/browse/SOLR-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203910#comment-13203910
]
Sami Siren commented on SOLR-3088:
----------------------------------
bq. and numShards as a collection property (rather than just a creation
property) doesn't make sense.
Yeah I agree. I just got confused when you mentioned (in the original issue
text) that something would have to be stored under /collections in zk.
So to summarize the scope of this issue once more:
Initiating the cluster/collection from the event of starting the first node:
The first node that joins the cluster will pass the desired slice count
(numShards System Property) and that number will be used to generate the
placeholders (slices containing 0 shards) for the specific collection in
cloudstate.
After that everything works pretty much as it is now, with one exception:
overseer does not look at the system property for determining how many slices
there should be but uses the slice count (the placeholders in the beginning)
from cloudstate.
> create shard placeholders
> -------------------------
>
> Key: SOLR-3088
> URL: https://issues.apache.org/jira/browse/SOLR-3088
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Yonik Seeley
> Fix For: 4.0
>
>
> When creating a new collection, a placeholder for each shard should be
> created.
--
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
