If you set maxFileCount to more than 1000 and more than 1000 are returned, the call will be billed as multiple transactions, as if you had made requests in a loop asking for 1000 at a time. The maximum number of files returned per transaction is 1000. NOTE: b2_list_file_names is a Class C transaction (see Pricing). Passing in 0 means to use the default of 100.
The default value is 100, and the maximum is 10000. "The maximum number of files to return from this call. My spidey sense nudges me towards the maxFileCount parameter: Backblaze list those API operations classified as Class C transactions, and their support team have suggested to me that the culprit for these kinds of problems is usually excessive invokations of the list_file_names API operation. Unfortunately, I'm getting a "Class C Transactions Cap Reached 100%" error message emailed to me from Backblaze every day 8mins after the task kicks off.
Have set up a daily task to sync 19,000 files with Backblaze B2 across a couple of buckets. Would appreciate a bit of help here please.
0 kommentar(er)
