[ https://issues.apache.org/jira/browse/SOLR-9511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542481#comment-15542481 ]
Pushkar Raste commented on SOLR-9511: ------------------------------------- We are planning to set num records in ulog to a very high number. If that number is too high, leader may run into issues (throw OOM), when replica asks for high number of updates. In such a case we will have to request updates in chunks/batches. In preparation of that, we should keep {{PeerSync.requestVersions()}} logic simple. This is ticket is to track effort for removing old way of using individual versions to request updates. > Retire using individual versions to request updates during PeerSync > ------------------------------------------------------------------- > > Key: SOLR-9511 > URL: https://issues.apache.org/jira/browse/SOLR-9511 > Project: Solr > Issue Type: Wish > Security Level: Public(Default Security Level. Issues are Public) > Affects Versions: master (7.0) > Reporter: Pushkar Raste > Priority: Minor > Fix For: master (7.0) > > > We started using version ranges to request updates during PeerSync in > [SOLR-9207| https://issues.apache.org/jira/browse/SOLR-9207]. Using version > ranges was also made default. > There is no need to have code that uses individual versions start Solr 7. > Decommission (remove unnecessary code) -- 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