[
https://issues.apache.org/jira/browse/SOLR-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520946#comment-16520946
]
Noble Paul commented on SOLR-12356:
-----------------------------------
{quote}Why? we don't care about search performance of this collection that
much, we only care about fault tolerance. Having a replica on every node seems
an overkill - if your cluster is likely to lose N-1 nodes you're in a deep
trouble anyway
{quote}
Imagine you have . an RF of 3 and you have 20 nodes. It's not uncommon to lose
3 nodes out of 20.
{quote}I disagree - actively hiding this from the users complicates the code
and prevents them from understanding how it works.
{quote}
The problem with system generated config coexisting with user created config is
that it leads to
* config bloat which leads to poor readability.
* Legacy configuration living in the cluster the user doesn't know how to
upgrade when something changes in the framework
OTOH, if we are maintaining that configuration hidden from users , we eliminate
this problem altogether. Another place where we apply these principles is the
implicitly registered responseWriters, requesthandlers, functions etc . We
could have left them in the {{solrconfig.xml}} and it would have caused the
same problems as I mentioned above. In short, I'm not very happy to see the
autoAddReplicas creating a huge blob of config in {{autoscaling.json}} which
the user is left to manage
> 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
