cl/tests: ClusterLinkingProgressVerifier fix #28436
Merged
Conversation
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
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a race condition in the ClusterLinkingProgressVerifier test that caused timeout errors when the consumer tried to read before the producer's offset map file was available. The fix ensures the producer's offset map is ready before creating the consumer and runs the consumer on the same node as the producer to avoid file access issues.
- Adds a wait for the producer's offset map file before creating the consumer
- Configures the consumer to run on the same nodes as the producer
- Reduces cluster node count from 8-10 to 7 across multiple tests (now that consumer runs on producer's node)
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tests/rptest/tests/cluster_linking_test_base.py | Adds wait for offset map and configures consumer to use producer's nodes |
| tests/rptest/tests/cluster_linking_e2e_test.py | Reduces num_nodes from 8-10 to 7 for multiple test methods |
| tests/rptest/scale_tests/cluster_linking_many_partitions_test.py | Reduces num_nodes from 8 to 7 for scale test |
Collaborator
Retry command for Build#75863please wait until all jobs are finished before running the slash command |
Collaborator
There are a class of failures that result in errors such as: ``` ducktape.errors.TimeoutError: Timed out waiting for status endpoint KgoVerifierConsumerGroupConsumer-0-140503148073056 to be available ``` This is due to: ``` time="2025-11-07T15:15:05Z" level=info msg="Reading with consumer group source-cg-source-topic" time="2025-11-07T15:15:05Z" level=error msg="More partitions in valid_offsets file than in topic!" ``` And the reason for that is that the consumer is running on a different node than the producer. The fix is in two parts: * Wait for the file before creating the consumer * Run the consumer on the same node as the producer Signed-off-by: Ben Pope <[email protected]>
BenPope
force-pushed
the
cl/test_replication_basic/time_out_waiting_for_KgoVerifierConsumerGroupConsumer
branch
from
6018b22 to
b916060
Compare
Member
Author
|
/ci-repeat 1 |
michael-redpanda
approved these changes
Nov 10, 2025
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.
There are a class of failures that result in errors such as:
This is due to:
And the reason for that is that the consumer is running on a different node than the producer.
The fix is in two parts:
Fixes https://redpandadata.atlassian.net/browse/CORE-14327
Fixes https://redpandadata.atlassian.net/browse/CORE-14518
Backports Required
Release Notes