[jira] [Updated] (SOLR-9689) Process updates concurrently during PeerSync

["Pushkar Raste (JIRA)" <ji...@apache.org>]

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

Pushkar Raste updated SOLR-9689:
--------------------------------
    Attachment: SOLR-9689.patch2

A new patch with configurable threshold for parallelism  

> Process updates concurrently during PeerSync
> --------------------------------------------
>
>                 Key: SOLR-9689
>                 URL: https://issues.apache.org/jira/browse/SOLR-9689
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Pushkar Raste
>         Attachments: SOLR-9689.patch, SOLR-9689.patch2
>
>
> This came up during discussion with [~shalinmangar]
> During {{PeerSync}}, updates are applied one a time by looping through the updates received from the leader. This is slow and could keep node in recovery for a long time if number of updates to apply were large. 
> We can apply updates concurrently, this should be no different than what could happen during normal indexing (we can't really ensure that a replica will process updates in the same order as the leader or other replicas).
> There are few corner cases around dbq we should be careful about. 



--
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