[
https://issues.apache.org/jira/browse/SOLR-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516767#comment-16516767
]
Andrzej Bialecki commented on SOLR-12356:
------------------------------------------
This collection is used not only for metrics, but also for autoscaling history
and for blobs. IMHO the benefits of always having this collection outweigh the
costs:
* I agree that components should fail gracefully if the collection is not
present - this is simple to implement and it's a good practice to do this
anyway.
* initially when only 1 node is present the replicationFactor is 1 - however,
we can use already existing mechanisms, such as {{AutoAddReplicasPlanAction}}
to automatically increase RF to a "safe" default eg. 3, or a percentage of live
nodes.
* autoscaling framework can automatically handle placing these replicas on
different physical machines, eg using IP-based rules.
* we already have an API to manage cluster properties, including collection
defaults - we can allow users to opt out of having this collection
> 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
