[
https://issues.apache.org/jira/browse/SOLR-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15642554#comment-15642554
]
Jan Høydahl commented on SOLR-7955:
-----------------------------------
Defaulting to number of live nodes in cluster would probably do. Then we'd need
to document that manual ADDREPLICA calls are necessary to achieve redundancy if
you start off with one node and later add nodes.
Ideally we should re-visit the former vision of being able to configure a
*desired state* for a collection, which the cluster (Overseer) will try to
achieve. Say you configure {{replicationFactor=3&stateType=desired}} in a
one-node cluster. Then you add nodes, and the Overseer issues ADDREPLICA
commands until condition is reached. Next, we could allow variables/functions
instead of absolute numbers, i.e. {{replicationFactor=nodeCount()}}. Of course
there are many issues to such an approach too, e.g. actions should probably
only trigger N seconds after the last add/remove command.
> Auto create .system collection on first request if it does not exist
> --------------------------------------------------------------------
>
> Key: SOLR-7955
> URL: https://issues.apache.org/jira/browse/SOLR-7955
> Project: Solr
> Issue Type: Improvement
> Reporter: Jan Høydahl
> Attachments: SOLR-7955.patch
>
>
> Why should a user need to create the {{.system}} collection manually? It
> would simplify instructions related to BLOB store if user could assume it is
> always there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
