[
https://issues.apache.org/jira/browse/SOLR-10962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068808#comment-16068808
]
Shalin Shekhar Mangar commented on SOLR-10962:
----------------------------------------------
Although from a solrconfig.xml perspective, moving commitReserveDuration to a
top-level attribute for ReplicationHandler is fine, I prefer that we do not
force users to add these configurations in solrconfig.xml and instead use a
well-known name in Config API to update these settings in the same way that we
can update autoCommit.maxTime etc. Editing solrconfig.xml by hand should never
be the answer to solve configurability in SolrCloud going forward.
> replicationHandler's reserveCommitDuration configurable in SolrCloud mode
> -------------------------------------------------------------------------
>
> Key: SOLR-10962
> URL: https://issues.apache.org/jira/browse/SOLR-10962
> Project: Solr
> Issue Type: New Feature
> Components: replication (java)
> Reporter: Ramsey Haddad
> Priority: Minor
> Attachments: SOLR-10962.patch, SOLR-10962.patch, SOLR-10962.patch
>
>
> With SolrCloud mode, when doing replication via IndexFetcher, we occasionally
> see the Fetch fail and then get restarted from scratch in cases where an
> Index file is deleted after fetch manifest is computed and before the fetch
> actually transfers the file. The risk of this happening can be reduced with a
> higher value of reserveCommitDuration. However, the current configuration
> only allows this value to be adjusted for "master" mode. This change allows
> the value to also be changed when using "SolrCloud" mode.
> https://lucene.apache.org/solr/guide/6_6/index-replication.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
