[
https://issues.apache.org/jira/browse/SOLR-16487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699242#comment-17699242
]
ASF subversion and git services commented on SOLR-16487:
--------------------------------------------------------
Commit c6706dfdbaa4b8c06de82b16d914d4f5d072298f in solr's branch
refs/heads/main from Justin Sweeney
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=c6706dfdbaa ]
SOLR-16487: Improve Pull Replica Interval (#1437)
* Updating replication polling to factor in if a new searcher is opened or not
as well as adding a test for poll interval logic
> Improve calculation of poll interval for replicas
> -------------------------------------------------
>
> Key: SOLR-16487
> URL: https://issues.apache.org/jira/browse/SOLR-16487
> Project: Solr
> Issue Type: Improvement
> Components: replication (java)
> Affects Versions: 9.0, 8.11.2
> Reporter: Justin Sweeney
> Assignee: Justin Sweeney
> Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Currently the polling for replication is fairly simply, but can lead to
> polling too often. As an example if you had the following config for commits:
> {code:java}
> <autoCommit>
> <maxTime>15000</maxTime>
> <openSearcher>false</openSearcher>
> </autoCommit>
> <autoSoftCommit>
> <maxTime>60000</maxTime>
> </autoSoftCommit> {code}
> The current logic would setup polling to be half of the autoCommit time, so
> poll every 7.5 seconds. However since a new searcher isn't opened, there will
> only be changes reflected every 60 seconds on the leader. We can make this
> logic a bit smarter knowing that the replication handler won't reflect
> changes until a new searcher is opened.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
