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

Jump to bottom

Upload to B2 churning through Class C Transactions #9417

Closed
cyberduck opened this issue Apr 6, 2016 · 3 comments
Closed

Upload to B2 churning through Class C Transactions #9417

cyberduck opened this issue Apr 6, 2016 · 3 comments
Labels
b2 Backblaze B2 Protocol Implementation bug fixed high priority
Milestone
4.9.1

Comments

@cyberduck
Copy link
Collaborator

72d76fe created the issue

Hi My 250GB upload to B2 via Cyberduck cut short when my Daily Class C Transactions hit their 2500 free cap.
I've since increased this to 1,000,000+, but in my attempt to resume my upload the following happened.

  1. It appears more API calls are being made and counted against my 1,000,000 for assessing files that have been uploaded and remain to upload. I'm not 100% sure if that is happening but I think it is.

  2. During TRAC-9948 Ignore permission denied when attempting to find multipart uploads. #1 the program crashed. It reported back the event automatically it appears.

  3. I got an error on a large file that is 1.3GB in size during the file prep. Not sure why.

  4. I noticed that the log drawer doesn't show past events until the log drawer is opened. This forced me to repeat my actions to see what the event was in the log.

  5. When I resumed my upload registers as 0B

The good news is that things resumed but it took two tries. Let me know what is going on with the Class C transactions for resumed uploads please.

Thanks

Jim
@cyberduck
Copy link
Collaborator Author

@dkocher commented

It is a known issue that we use too many Class C transactions because we use a single upload URI (b2_get_upload_url) for each file.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please attach the file cyberduck.log and the crash reports saved in a folder named CrashReporter in the application support directory.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 345fa16.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
b2 Backblaze B2 Protocol Implementation bug fixed high priority
Projects
None yet
Milestone
4.9.1
Development

No branches or pull requests
1 participant
@cyberduck