vigyasharma opened a new pull request, #14443: URL: https://github.com/apache/lucene/pull/14443
In segment based replication systems, a large replication payload (checkpoint) can induce heavy page faults, cause thrashing for in-flight search requests, and affect overall search performance. A potential way to handle these bursts, is to leverage multiple commit points in the Lucene index. Instead of refreshing to the latest commit for a large replication payload, searchers can intelligently select the commit point that they can safely absorb. By processing through multiple such points, searchers can eventually get to the latest commit, without incurring too many page faults. This change lets users define a commit selection strategy, controlling which commit the searcher manager refreshes on. Addresses #14219 **Usage:** To incrementally refresh through multiple commit points until searcher is current with its directory: - Define a commit selection strategy using the `RefreshCommitSupplier` interface. - Update searcher managers with this strategy via `setRefreshCommitSupplier()` - Invoke `maybeRefresh()` or `maybeRefreshBlocking` in a loop until `isSearcherCurrent()` returns true. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
