Skip to content

Reindexing Remote Tests#143461

Closed
joshua-adams-1 wants to merge 8 commits intoelastic:mainfrom
joshua-adams-1:reindexing-set-test-cluster-feature
Closed

Reindexing Remote Tests#143461
joshua-adams-1 wants to merge 8 commits intoelastic:mainfrom
joshua-adams-1:reindexing-set-test-cluster-feature

Conversation

@joshua-adams-1
Copy link
Copy Markdown
Contributor

#142494 introduced reindexing logic to determine the remote version before opening a PIT. However, since the tests default NodeFeatures to false, there was no test coverage of this new code branch. This change modifies a number of unit and integration tests to run against the PIT code, to provide coverage. Note that this only adds coverage for logic added in #142494. All subsequent changes shall add coverage from unit / integration tests as and when needed.

Relates: https://github.com/elastic/elasticsearch-team/issues/2088

Changes the Reindexer to use a cluster feature check to guard the PIT
changes, rather than a feature flag. This will be safer when rolling out
 the reindexing changes during a rolling upgrade, so that one node does
 not begin a reindex using PIT before the other nodes are capable of
 running the corresponding PIT searches.
Extends ReindexFromRemoteWithAuthTests to be parameterised to run both
with scroll, and with point-in-time searching enabled.

Relates: elastic/elasticsearch-team#2088
@joshua-adams-1 joshua-adams-1 self-assigned this Mar 3, 2026
@joshua-adams-1 joshua-adams-1 added >test Issues or PRs that are addressing/adding tests :Distributed/Reindex Issues relating to reindex that are not caused by issues further down labels Mar 3, 2026
@joshua-adams-1
Copy link
Copy Markdown
Contributor Author

I don't think this is needed. Running tests locally defaults to the feature flag being true, which leaves the feature flag = false branches as untested. However, I can add test-release to the PR to run it through twice, with both snapshot and release mode as true, and this should catch any failing tests for me. Adding a PR label is also quicker and easier than trying to find individual tests to force to run twice through. This can of course be opened again later if necessary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed/Reindex Issues relating to reindex that are not caused by issues further down >test Issues or PRs that are addressing/adding tests v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants