-
Notifications
You must be signed in to change notification settings - Fork 24.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CCR should check historyUUID in every read request (#65841)
Today, CCR only checks the historyUUID of the leader shard when it has operations to replicate. If the follower shard is already in-sync with the leader shard, then CCR won't detect if the historyUUID of the leader shard has been changed. While this is not an issue, it can annoy users in the following situation: 1. The follower index is in-sync with the leader index 2. Users restore the leader index from snapshots 3. CCR won't detect the issue and report ok in its stats API 4. CCR suddenly stops working when users start indexing to the leader index 5. This commit makes sure that we always check historyUUID in every read-request so we can detect and report the issue as soon as possible. Backport of #65841
- Loading branch information
Showing
2 changed files
with
57 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters