You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've seen this error, but only in one case. It looks like it's calling write before setup.
I tried adding @gs_bucket = initialize_bucket unless @gs_bucket before the write but it didn't help. I don't get the error, but it doesn't write the file, timeout or error in another way.
I am writing to a bucket in the US and only experience this issue from europe-west1. It works fine from my instances in us-central1 and AWS us-east-1.
All the instances are setup with puppet so I doubt there is any environmental differences.
Any ideas?
The text was updated successfully, but these errors were encountered:
I only had this error when I used a non-existing bucket name.
I'm working on a guard method which checks the specified bucket in configuration time. You can expect it in a few days.
Until then just double check if you can reach your bucket from the mentioned server.
I've diagnosed this to be due to using 512MB buffers. If I split an existing buffer into smaller chunks, the files uploaded without a problem.
The only difference with my European instances was that they were smaller and had 1.8GB RAM. I've upgraded them to instances with more RAM and 512MB buffers work fine again.
I'm assuming there is an issue in the Google Cloud client that causes the create_file operation to hang at a point before the timeout (which seems to be 120s by default, on a separate note maybe you could make that configurable).
I don't think you can do anything about this, but we can leave this ticket open as you have identified the cause of the error message as a genuine bug.
I've seen this error, but only in one case. It looks like it's calling
write
beforesetup
.I tried adding
@gs_bucket = initialize_bucket unless @gs_bucket
before the write but it didn't help. I don't get the error, but it doesn't write the file, timeout or error in another way.I am writing to a bucket in the US and only experience this issue from europe-west1. It works fine from my instances in us-central1 and AWS us-east-1.
All the instances are setup with puppet so I doubt there is any environmental differences.
Any ideas?
The text was updated successfully, but these errors were encountered: