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

Error: error copying block from local to remote backend #3468

Closed
flenoir opened this issue Mar 6, 2024 · 2 comments
Closed

Error: error copying block from local to remote backend #3468

flenoir opened this issue Mar 6, 2024 · 2 comments
Labels
stale Used for stale issues / PRs

Comments

@flenoir
Copy link

flenoir commented Mar 6, 2024

Describe the bug
Hi, after a while on using Tempo. I get this kind of error messages :
I get an error message "err="error copying block from local to remote backend: error writing object to s3 backend, object single-tenant/e4e7ad1b-c753-4496-82f6-87e56504755a/data.parquet: Check if quota has been exceeded or object has too many versions"

This may be related to the fact that Compactor pod did a restart

To Reproduce
Use Tempo as expected and store data on a s3 bucket

Expected behavior
Not having this error message

Environment:

  • Infrastructure: Kubernetes
  • Deployment tool: helm
  • S3 Buckets are hosted on Dell ECS
@joe-elliott
Copy link
Member

I have never used Dell ECS before nor have we ever seen that error. Did you check what the error message suggested?

Copy link
Contributor

github-actions bot commented May 6, 2024

This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.

@github-actions github-actions bot added the stale Used for stale issues / PRs label May 6, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Used for stale issues / PRs
Projects
None yet
Development

No branches or pull requests

2 participants