objstore: fix read position on retry when reading a file range using s3

[D3Hunter]

What problem does this PR solve?

Issue Number: close #50451

Problem Summary:

What changed and how does it work?

when reading a file range using s3, the pos must be set, as we will use it as the start position when retry

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @D3Hunter. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 74.8451%. Comparing base (ba94321) to head (faad6bb).
Report is 309 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59694        +/-   ##
================================================
+ Coverage   72.9585%   74.8451%   +1.8866%     
================================================
  Files          1697       1743        +46     
  Lines        468909     477049      +8140     
================================================
+ Hits         342109     357048     +14939     
+ Misses       105741      97531      -8210     
- Partials      21059      22470      +1411     

Flag	Coverage Δ
integration	48.6472% <0.0000%> (?)
unit	72.5023% <50.0000%> (+0.0395%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	∅ <ø> (∅)
parser	∅ <ø> (∅)
br	62.3479% <50.0000%> (+15.8814%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[D3Hunter]

/retest

[tiprow]

@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Benjamin2037]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-02-21 11:21:02.695597478 +0000 UTC m=+9210.648755738: ☑️ agreed by tangenta.
• 2025-02-21 15:41:09.144053185 +0000 UTC m=+24817.097211450: ☑️ agreed by Benjamin2037.

[D3Hunter]

/retest

[tiprow]

@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, Leavrth, tangenta

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• br/pkg/storage/OWNERS [Benjamin2037,Leavrth]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[D3Hunter]

/cherry-pick release-8.1-20250226-v8.1.2

[ti-chi-bot]

@D3Hunter: new pull request created to branch release-8.1-20250226-v8.1.2: #59766.

In response to this:

/cherry-pick release-8.1-20250226-v8.1.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[D3Hunter]

/cherry-pick feature/release-8.1-gsort-test

[ti-chi-bot]

@D3Hunter: new pull request created to branch feature/release-8.1-gsort-test: #59853.

In response to this:

/cherry-pick feature/release-8.1-gsort-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #60054.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #60055.

[ti-chi-bot]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against pingcap/tidb#release-8.5 from head ti-chi-bot:cherry-pick-59694-to-release-8.5: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between pingcap:release-8.5 and ti-chi-bot:cherry-pick-59694-to-release-8.5"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}