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

[fix](backup) Automatic adapt upload/download snapshot batch size #44560

Merged
merged 1 commit into from
Nov 26, 2024

Conversation

w41ter
Copy link
Contributor

@w41ter w41ter commented Nov 25, 2024

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

The original backup_upload_task_num_per_be and restore_download_task_num_per_be would not adapt the different num of snapshots, a large UploadTask or DownloadTask might exceed the threshold of thrift_max_message_size and failed forever.

This PR changes these options to adapt the number of snapshots automatically.

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.

Now each the number of snapshots assigned to a download/upload task is limited, and no num limitations of download/upload tasks are applied.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@w41ter
Copy link
Contributor Author

w41ter commented Nov 26, 2024

run buildall

@w41ter w41ter requested review from dataroaring and nextdreamblue and removed request for dataroaring November 26, 2024 02:13
@w41ter
Copy link
Contributor Author

w41ter commented Nov 26, 2024

run buildall

Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

PR approved by at least one committer and no changes requested.

@github-actions github-actions bot added approved Indicates a PR has been approved by one committer. reviewed labels Nov 26, 2024
Copy link
Contributor

PR approved by anyone and no changes requested.

@dataroaring dataroaring merged commit 0a61efa into apache:master Nov 26, 2024
23 of 25 checks passed
github-actions bot pushed a commit that referenced this pull request Nov 26, 2024
…4560)

The original `backup_upload_task_num_per_be` and
`restore_download_task_num_per_be` would not adapt the different num of
snapshots, a large `UploadTask` or `DownloadTask` might exceed the
threshold of `thrift_max_message_size` and failed forever.

This PR changes these options to adapt the number of snapshots
automatically.
github-actions bot pushed a commit that referenced this pull request Nov 26, 2024
…4560)

The original `backup_upload_task_num_per_be` and
`restore_download_task_num_per_be` would not adapt the different num of
snapshots, a large `UploadTask` or `DownloadTask` might exceed the
threshold of `thrift_max_message_size` and failed forever.

This PR changes these options to adapt the number of snapshots
automatically.
dataroaring pushed a commit that referenced this pull request Nov 27, 2024
@w41ter w41ter deleted the adapt_batch_size branch November 27, 2024 02:50
yiguolei pushed a commit that referenced this pull request Nov 27, 2024
…4560)

The original `backup_upload_task_num_per_be` and
`restore_download_task_num_per_be` would not adapt the different num of
snapshots, a large `UploadTask` or `DownloadTask` might exceed the
threshold of `thrift_max_message_size` and failed forever.

This PR changes these options to adapt the number of snapshots
automatically.
dataroaring pushed a commit that referenced this pull request Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by one committer. dev/2.1.8-merged dev/3.0.4-merged reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants