CCR follower index needs to copy transport version from CCR leader index#145035
Merged
jdconrad merged 6 commits intoelastic:mainfrom Mar 26, 2026
Merged
CCR follower index needs to copy transport version from CCR leader index#145035jdconrad merged 6 commits intoelastic:mainfrom
jdconrad merged 6 commits intoelastic:mainfrom
Conversation
…follow CcrRepository.getSnapshotIndexMetaData builds the follower's IndexMetadata from scratch using IndexMetadata.builder(String) and manually copies settings, mappings, and routing info from the leader. However, it never copied the transport_version field, leaving it at TransportVersion.ZERO on every newly created follower index. This caused the Upgrade Assistant's percolator deprecation check (reindexRequiredForPercolatorFields) to continuously fire on follower indices because the check compares transport_version / 1000 buckets, and bucket 0 is always less than the current minor release bucket. The fix copies the leader's transport_version into the follower's IndexMetadata during follow bootstrapping so that the follower correctly reflects the version at which the leader index was created or last reindexed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
jdconrad
added
>bug
:Distributed/CCR
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
elasticsearchmachine
added
Team:Distributed
Collaborator
|
Hi @jdconrad, I've created a changelog YAML for you. |
Replace docs/changelog/144973.yaml with the correct docs/changelog/145035.yaml which reflects the actual PR number. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
jdconrad
added a commit
to jdconrad/elasticsearch
that referenced
this pull request
Mar 26, 2026
…dex (elastic#145035) Currently, when adding a follower index to a leader index using CCR, transport version is not copied which leads to errors in the upgrade assistant.
jdconrad
added a commit
to jdconrad/elasticsearch
that referenced
this pull request
Mar 26, 2026
…dex (elastic#145035) Currently, when adding a follower index to a leader index using CCR, transport version is not copied which leads to errors in the upgrade assistant.
jdconrad
added a commit
to jdconrad/elasticsearch
that referenced
this pull request
Mar 26, 2026
…dex (elastic#145035) Currently, when adding a follower index to a leader index using CCR, transport version is not copied which leads to errors in the upgrade assistant.
Collaborator
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, when adding a follower index to a leader index using CCR, transport version is not copied which leads to errors in the upgrade assistant.