[ https://issues.apache.org/jira/browse/SOLR-10962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064688#comment-16064688 ]
Christine Poerschke commented on SOLR-10962: -------------------------------------------- At present we can have a _master_ or a _slave_ or _master and slave_ sections in the request handler configuration i.e. {code} <requestHandler name="/replication" class="solr.ReplicationHandler"> <lst name="master"> <str name="commitReserveDuration">...</str> ... </lst> </requestHandler> {code} or {code} <requestHandler name="/replication" class="solr.ReplicationHandler"> <lst name="slave"> ... </lst> </requestHandler> {code} or {code} <requestHandler name="/replication" class="solr.ReplicationHandler"> <lst name="master"> <str name="commitReserveDuration">...</str> ... </lst> <lst name="slave"> ... </lst> </requestHandler> {code} and with the addition of a _cloud_ section the number of (valid and invalid) combinations of sections would increase. Instead of a new _cloud_ section {code} <requestHandler name="/replication" class="solr.ReplicationHandler"> <lst name="cloud"> <str name="commitReserveDuration">...</str> </lst> </requestHandler> {code} with (for now) just the one _commitReserveDuration_ element, how about making _commitReserveDuration_ a top-level element i.e. in cloud mode {code} <requestHandler name="/replication" class="solr.ReplicationHandler"> <str name="commitReserveDuration">...</str> </requestHandler> {code} and {code} <requestHandler name="/replication" class="solr.ReplicationHandler"> <str name="commitReserveDuration">...</str> <lst name="master"> ... </lst> ... </requestHandler> {code} in other modes? _master.commitReserveDuration_ would be supported but deprecated for a transition period and eventually it would go away. > 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 > > > 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