Skip to content
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

SNOW-143538: We keep getting error 402001 - Network error. Could not reach S3/Blob. #85

Closed
Ginden opened this issue Mar 9, 2020 · 5 comments
Milestone

Comments

@Ginden
Copy link

Ginden commented Mar 9, 2020

System:
Node v10.18.0
npm v6.13.4
Ubuntu 18.04.3 LTS
[email protected]

What did you do?

We are running code like:

      this.snowflake.execute({
        sqlText,
        binds,
        streamResult: true,
        complete: done,
      })

Result set is around 500k rows.

  1. What did you expect to see?
    Working properly.

  2. What did you see instead?

We are randomly seeing error:

 2020-03-09T10:50:44.794Z - error: Network error. Could not reach S3/Blob. NetworkError: Network error. Could not reach S3/Blob.
     at createError (/app/node_modules/snowflake-sdk/lib/errors.js:524:15)
     at Object.exports.createNetworkError (/app/node_modules/snowflake-sdk/lib/errors.js:249:10)
     at Object.callback (/app/node_modules/snowflake-sdk/lib/services/large_result_set.js:72:24)
     at Request._callback (/app/node_modules/snowflake-sdk/lib/http/base.js:107:19)
     at self.callback (/app/node_modules/request/request.js:185:22)
     at Request.emit (events.js:198:13)
     at Request.EventEmitter.emit (domain.js:448:20)
     at Timeout._onTimeout (/app/node_modules/request/request.js:852:16)
     at ontimeout (timers.js:436:11)
     at tryOnTimeout (timers.js:300:5)

Unfortunely, there isn't reliable way to trigger it.

How should we debug from this place?

@github-actions github-actions bot changed the title We keep getting error 402001 - Network error. Could not reach S3/Blob. SNOW-143538: We keep getting error 402001 - Network error. Could not reach S3/Blob. Mar 9, 2020
@sfc-gh-stakeda
Copy link
Contributor

Added to the backlog.

sfc-gh-stakeda added a commit that referenced this issue Apr 7, 2020
Co-authored-by: Michał Wadas <[email protected]>
This attempts to mitigate #85
@sfc-gh-stakeda sfc-gh-stakeda added this to the v1.5.2 milestone Apr 7, 2020
sfc-gh-abhatnagar pushed a commit that referenced this issue Apr 7, 2020
Co-authored-by: Michał Wadas <[email protected]>
This attempts to mitigate #85
@offero
Copy link

offero commented Aug 5, 2020

Just hit this too
[email protected]

Which version will have the fix?

@haggholm
Copy link

We are experiencing this problem with version 1.6.14 of the library, i.e. after the fix was implemented. Can you provide any more information about the root cause of the problem to better help us understand how to work around or address it?

@mikelecomte
Copy link

Seeing this intermittently with 1.6.23, as of a couple days ago. Our process has been running fine for about 3 weeks prior to this.

@Ginden
Copy link
Author

Ginden commented Jul 31, 2023

Our workaround was to spin Python process and communicate with it through IPC, as Python driver doesn't have this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants