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

Backup rename timeout error #50989

Closed
dengliu opened this issue Sep 12, 2024 · 2 comments
Closed

Backup rename timeout error #50989

dengliu opened this issue Sep 12, 2024 · 2 comments
Assignees
Labels
type/bug Something isn't working

Comments

@dengliu
Copy link
Contributor

dengliu commented Sep 12, 2024

Steps to reproduce the behavior (Required)

Error: Fail to rename file
Source: s3a://sss_879158/020000000000011c5944ad1dbbcfc5f88c123e81e2cc1fba_0.dat.part
Target: s3a://sss8/020000000000011c5944ad1dbbcfc5f88c123e81e2cc1fba_0.dat.9ace0c9794abda71dcc52a3162c26232
Message: Fail to copy from src to target, msg: curlCode: 28, Timeout was reached

Expected behavior (Required)

No error.
Potential fix could be using checksum to check ensure the integrity of the uploaded file

Real behavior (Required)

StarRocks version (Required)

  • You can get the StarRocks version by executing SQL select current_version()
@dengliu dengliu added the type/bug Something isn't working label Sep 12, 2024
@srlch
Copy link
Contributor

srlch commented Oct 22, 2024

#48860 introduce a individual param to adjust the rename timeout, will try to optimize this problem ASAP.

@kevincai
Copy link
Contributor

fixed in #52394, rename op is removed if the backup repository is an S3-compatible storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants