-
Notifications
You must be signed in to change notification settings - Fork 144
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
Connection broken: error 104, ECONNRESET #12
Comments
797/800 isn't bad :) |
I agree it's not that bad - especially since I think I opened a few more files, so it's closer to 1000. Since you're open to it, yes, I can try my hand at a PR. Can't guarantee it'll come today though. |
The try/retry should go around this line: https://github.com/dask/gcsfs/blob/master/gcsfs/core.py#L298 |
OK to close? |
Absolutely! |
@martindurant can you reopen the issue ? I was misled in thinking that error 104 was not caught as retriable but it is the logging of it that is confusing, especially when one looks at Stackdriver logging - we use gcsfs in Cloud Functions. In particular:
If retriable, would we want to log as an exception ? Warning no good for us as this is mapped to Error in SD logging too. I would remove the |
How about:
|
Very good ! The more - "switchable" - info the better ! |
@martindurant Can you reopen the issue to include your latest code proposal ? |
This change was made in 323ac55 ( https://github.com/dask/gcsfs/blob/master/gcsfs/core.py#L474 ) |
Thx ! Had missed that. |
I used gcsfs to read about 800 files and it failed for 3 of them with this error:
The call stack looks like this:
From the outside it looks like sometimes GCS has some sort of transient errors and GCSFS ought to be able to survive those and retry.
The text was updated successfully, but these errors were encountered: