[jira] [Updated] (SOLR-8656) PeerSync should use same nUpdates everywhere

["Anshum Gupta (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anshum Gupta updated SOLR-8656:
-------------------------------
    Fix Version/s: 5.5.1
                   6.0

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org