Ramsey Haddad created SOLR-8656: ----------------------------------- Summary: 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: 5.4.1, Trunk Reporter: Ramsey Haddad Priority: Minor
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