Hi all,
Recently, I found the following configuration in a solrcloud cluster ver.
8.11.2 (2 core 32GB RAM).
<autoCommit>
<maxDocs>${solr.autoCommit.maxDocs:-1}</maxDocs>
<maxTime>${solr.autoCommit.maxTime:60000}</maxTime>
<openSearcher>false</openSearcher>
</autoCommit>
<autoSoftCommit>
* <maxDocs>${solr.autoSoftCommit.maxDocs:1}</maxDocs>*
<maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
</autoSoftCommit>
my attention was captured by autoSoftCommit.maxDocs set to 1.
IMHO having softcommit maxdoc set to 1 is a (little?) dangerous
configuration.
This implies that for each updated document all SolrCloud nodes have to be
updated...
Not sure what happens behind the scene, and that's the question.
In other words, consider that the solrcloud cluster receives a spike of
updates (thousands of documents or more), for each document a softcommit is
triggered for the whole cluster, what do you think, what happens?
Best regards,
Vincenzo
--
Vincenzo D'Amore
