Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

e2e_topic_recovery_test: have s3 check the delta offset #8856

Merged
merged 1 commit into from
Feb 15, 2023

Conversation

andrwng
Copy link
Contributor

@andrwng andrwng commented Feb 14, 2023

The test currently waits for a target Redpanda offset to be uploaded, and then checks that the correct number of Kafka offsets are consumable. This isn't quite right, since we also need to take into account config batches in our Redpanda offsets.

This updates the test to take into account the 'delta_offset_end' field of the last offset, which should give us an accurate view of the number of Kafka data batches in the topic.

Fixes #8876

Backports Required

  • none - not a bug fix
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v22.3.x
  • v22.2.x
  • v22.1.x

UX Changes

Release Notes

  • none

The test currently waits for a target Redpanda offset to be uploaded,
and then checks that the correct number of Kafka offsets are consumable.
This isn't quite right, since we also need to take into account config
batches in our Redpanda offsets.

This updates the test to take into account the 'delta_offset_end' field
of the last offset, which should give us an accurate view of the number
of Kafka data batches in the topic.
@jcsp
Copy link
Contributor

jcsp commented Feb 14, 2023

Nice.

This was for a test failure, right? Can you link the issue with a Fixes line please.

@andrwng andrwng merged commit 30fe679 into redpanda-data:dev Feb 15, 2023
@andrwng
Copy link
Contributor Author

andrwng commented Feb 15, 2023

/backport v22.3.x

@andrwng
Copy link
Contributor Author

andrwng commented Feb 15, 2023

/backport v22.2.x

@vbotbuildovich
Copy link
Collaborator

Failed to run cherry-pick command. I executed the below command:

git cherry-pick -x 2cc199c0e64cd8e0293ab3398c7ceef04d7b5bc5

Workflow run logs.

@vbotbuildovich
Copy link
Collaborator

Failed to run cherry-pick command. I executed the below command:

git cherry-pick -x 2cc199c0e64cd8e0293ab3398c7ceef04d7b5bc5

Workflow run logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI Failure (incorrect number of records consumed) in EndToEndTopicRecovery.test_restore
3 participants