[
https://issues.apache.org/jira/browse/SOLR-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475926#comment-16475926
]
Shawn Heisey commented on SOLR-12356:
-------------------------------------
The only issues I can see related to doing this automatically is how
replicationFactor is decided, and how to prevent multiple replicas from ending
up on the same node. When somebody decides to run multiple nodes per host,
ensuring proper replica placement is particularly important.
The first time an overseer starts in a cloud, there's probably only going to be
one Solr node, so it won't be possible to create the collection with a
replicationFactor higher than 1. How do we handle that? When nodes are added,
how do we decide whether to automatically add a replica? My preference would be
to do the add, but users may disagree, especially if they add a node in a
location with limited bandwidth.
> Always auto-create ".system" collection when in SolrCloud mode
> --------------------------------------------------------------
>
> Key: SOLR-12356
> URL: https://issues.apache.org/jira/browse/SOLR-12356
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andrzej Bialecki
> Priority: Major
>
> The {{.system}} collection is currently used for blobs, and in SolrCloud mode
> it's also used for autoscaling history and as a metrics history store
> (SOLR-11779). It should be automatically created on Overseer start if it's
> missing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
