[ https://issues.apache.org/jira/browse/SOLR-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252469#comment-15252469 ]
ASF subversion and git services commented on SOLR-8656: ------------------------------------------------------- Commit 9f7bd67d2d34be1548fff6f2f44a4146b9d28b13 in lucene-solr's branch refs/heads/branch_5_5 from markrmiller [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9f7bd67 ] SOLR-8656: PeerSync should use same nUpdates everywhere. > PeerSync should use same nUpdates everywhere > -------------------------------------------- > > Key: SOLR-8656 > URL: https://issues.apache.org/jira/browse/SOLR-8656 > Project: Solr > Issue Type: Bug > Components: SolrCloud > Affects Versions: master, 5.4.1 > Reporter: Ramsey Haddad > Assignee: Anshum Gupta > Priority: Minor > Fix For: master, 6.0, 5.5.1 > > Attachments: solr-8656.patch > > > PeerSync requests information on the most recent nUpdates updates from > another instance to determine whether PeerSync can succeed. The value of > nUpdates can be customized in solrconfig.xml: > UpdateHandler.UpdateLog.NumRecordsToKeep. > PeerSync can be initiated in a number of different paths. One path to start > PeerSync (leader-initiated sync) is incorrectly still using a hard-coded > value of nUpdates=100. > This change fixes leader-initiated-sync code path to also pick up the value > of nUpdates from the customized/configured value. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org