google-cloud-go: storage: read -> connection reset by peer

'smee again 😄 😛

I’m probably missing something, but I’ve hit this snag and thought I’d ask if it’s something occasional, or if it’s by design, and I missed the docs for it.

I was slowly streaming a download from GCS to GCE, processing some data and pushing stuff back up to GCS. After about 10-15 minutes, my reader crashed with read tcp 64.233.182.132:443: connection reset by peer. I haven’t really found any reason why GCS would disrupt a running download (apart from maybe deeming it too slow). Is there some time/rate/whatev limit that CGS imposes, or should I look for the culprit somewhere else?

Thanks

About this issue

Original URL
State: closed
Created 9 years ago
Reactions: 4
Comments: 19 (11 by maintainers)

Most upvoted comments

I get the same error as OP @karalabe and @brianmhunt. Connection reset by peer

It happens during:

storage.bucket(bucket).get_blob(path)
and bigquery_client.insert_rows(table, rows_to_insert).

This is running Google Cloud Functions with Python 3.7 and google-cloud-storage==1.11.0.

Not all the time, about 10% failure rate. Function deployed to us-east1 (I also tried us-central1, about the same).

cmey on Sep 28, 2018