[
https://issues.apache.org/jira/browse/SOLR-16487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697930#comment-17697930
]
Justin Sweeney commented on SOLR-16487:
---------------------------------------
(y)Thanks [~dsmiley] for the pointer, made that request.
I agree that an approach where post-commit the leader would provide a
notification to replicas would be a better approach. I propose this change as a
short term fix to at least make polling more efficient and I can open a new
issue to look into replication based on a notification from the leader. This
would be interesting to dig into, but will take a bit more time.
> 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: 40m
> 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]
