Suddenly not been able to access files via presigned URL generate via boto3 in python, its throwing
Suddenly not been able to access files via presigned URL generate via boto3 in python, its throwing me NoSuchKey error
USounds like either the access key used for signing doesnt exist or the object youre trying to access doesnt exist
MHi every one
I am new to R2 storage
Can any one tell me hot can i download specific folder from R2.
Or make any folder shareable so other use see that and download that folder.
I am new to R2 storage
Can any one tell me hot can i download specific folder from R2.
Or make any folder shareable so other use see that and download that folder.
Xhi everyone
KThe limit of 1,000? There isn't a way, you have to paginate
KThe list API is the same as S3
IHi Guys! stupid question. I recently decided to give it a try with logpush. so i need to create an R2 bucket. i created it. but I cannot access it, I always receive "remote error: tls: handshake failure". I tried adding a logpush to r2 destination and also with postman R2 collection. What am I missing?
H"Great news!!"
Someone else has the same issue as me, so this is clearly not specific to my account...
(Frankly, I am slightly relieved... ¯\_(ツ)_/¯)
https://community.cloudflare.com/t/old-r2-file-not-accessible-anymore/604487
Someone else has the same issue as me, so this is clearly not specific to my account...
(Frankly, I am slightly relieved... ¯\_(ツ)_/¯)
https://community.cloudflare.com/t/old-r2-file-not-accessible-anymore/604487
HAnyway, gotta hit the hay. :)
CHello everyone, anyone knows if there is going to be a Intelligent Tiering as in S3? If yes, someone knows any ETA? Mostly for something like Glacier Tiers
Whello!
Wnewbie question here - if I upload my files to R2, can I somehow point stream to it for processing - so we can avoid storing the same file twice in 2 parts of the network?
Wor perhaps set stream up to use a dedicated bucket or folder from which to take video files to be processed?
Wthis in reply to. my question?
Wyes - the intent is to upload first to r2 and then offer it for streaming a few minutes later
C@supernekonyannyan @erisachu @unsmart latest news on the uploading problems The customer service team stated that there is a limit on R2 and that it can't handle more than 300 uploads at this time. They said it was their long-term plan to handle higher volumes, but they didn't say when it would be fixed.
I was more hopeful about R2, but it won't work for us, so we need to stick to Google Storage or something else.
I was more hopeful about R2, but it won't work for us, so we need to stick to Google Storage or something else.
Cprobably, they didn't give much clarity, just stated that its backend limitation.
EIts not a hard written limit and more of a "if you go too high, R2 starts to break"
EEnjoy
EThat would work
EWhich support on which ticket? I am in Support myself
EThats not a direct quote from a ticket, its what Chandan wrote
KMight be 3075872
KBucket sharding has been the go-to for a long time in regards to the use-case of lots of concurrency for a single bucket.
DWhen using aws4fetch, is there any downside to signing the
cf-worker header?
CIs there any way to overcome this, apart from bucket sharding?
ENo, as noted on the ticket, the product needs to be improved
C#3075872
Cyes, simultaneous uploads
Cticket id #3075872, same ticket which you were looking into it.
CI wrote the above, but all I can understand from below reply, we already retrying but its just making it worse for reads too.
EIt's due to limitations and resiliency of the product, but it isn't necessarily "300 concurrent = break", it's more nuanced than that. If you aren't able to work around the issue with retries or bucket sharding then I'm afraid that may mean that the product isn't currently well suited to your use-case
Cwe process almost 1-2 million of files a day, what type sharding can work for this?
EYou would have to split them into different buckets
EAs each bucket is "separate" as far as this issue is concerned
Cyeah, I'm not saying hard limit, but its just my observation, where our application almost unusable.
EUnderstood
ESorry about that, we checked all we could but it's just how it is at the moment
CIs this something that they are currently working on? Is there any public Roadmap people could see to track such things?
Ceven if we tried to shard to lowest possible way for our architecture (per client), it will be more 1200 buckets, but errors coming for small traffic of our actual traffic, we didn't even had a chance to put all traffic.
Calso per account 1000 bucket limit is there
