[
https://issues.apache.org/jira/browse/SOLR-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203503#comment-13203503
]
Sami Siren commented on SOLR-3088:
----------------------------------
bq. the cluster should be self-describing so that one can start up a node and
say "go join this cluster"
Do you mean that the new node would automatically discover from the
placeholders how many cores it needs to start?
Now everything works just the opposite way: nodes create the cores they are
configured to do (solr.xml/CoreAdminHandler) and the overseer just assigns them
a shard id as they come in. I assume everything could still work this way when
using the placeholders but it sounds a bit awkward.
bq. I imagine the placeholders should be both in the ZK structure under
/collections and in clusterstate
What did you have in mind that should be stored under /collections?
In earlier versions I had overseer read the target number of slices from the
collection node (/collections/collection1 for example) but that was later
removed in favor of the system property.
What should be in charge of creating a new collection? Now you can do it for
example through CoreAdminHandler by simply adding a core into a collection that
does not yet exist, I believe you can do this also through editing solr.xml.
> 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
