[
https://issues.apache.org/jira/browse/SOLR-13604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878044#comment-16878044
]
Andrzej Bialecki commented on SOLR-13604:
------------------------------------------
+1. Even with single replica collections this should be an error because you
can easily add more replicas after you've created the collection, at which
point things will go south (even more).
> if updateLog isn't in config, complain loudly if it's needed for SolrCloud
> --------------------------------------------------------------------------
>
> Key: SOLR-13604
> URL: https://issues.apache.org/jira/browse/SOLR-13604
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 7.1
> Reporter: David Smiley
> Priority: Minor
>
> The updateLog can be commented out, and SolrCloud will only contain this
> error:
> 2019-07-03 16:15:55.907 ERROR (qtp214649627-92) [c:gettingstarted s:shard1
> r:core_node4 x:gettingstarted_shard1_replica_n2] o.a.s.c.SyncStrategy No
> UpdateLog found - cannot sync
> I suspect it's truly required in which Solr should complain more loudly about
> this -- throw an exception. For single replica collections, I suppose it's
> fine (not an error?)? Granted then there could be an issue of adding
> replicas later (unless pull type; those are fine). Even if multi-replica
> SolrCloud can usefully work without an updateLog (news to me) then maybe we
> shouldn't log an error, although the lack of an updateLog would probably be
> an oversight that would be hard to track down the root cause of.
> I wish the updateLog altogether could be more optional but that's another
> conversation.
--
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
