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

[DATABRICKS ERROR]: "FetchError: socket hang up" #260

Open
kumarav16 opened this issue Jun 10, 2024 · 4 comments
Open

[DATABRICKS ERROR]: "FetchError: socket hang up" #260

kumarav16 opened this issue Jun 10, 2024 · 4 comments

Comments

@kumarav16
Copy link

Hi, we have encountered a socket hang-up error while performing a longevity test.
we have used Node version: 20.11.1 and @databricks/sql package version: 1.7.1

kindly find the below error and screenshot for the same:

" error occurred while resolving the DB query!, FetchError: request to https://adb-4989540552326160.0.azuredatabricks.net/sql/1.0/warehouses/d332f02ce1613e30 failed, reason: socket hang up"

image

Please help us to resolve the issue and let us know in-case of more information needed.

@kravets-levko
Copy link
Contributor

Hi @kumarav16! I will ask you few question that crossed my mind right away:

  • do you see this error with latest version of the library?
  • do you use proxy?
  • on which stage (opening session, running query, getting the result, etc.) this is happening?
  • how large is your result set?

But it would be perfect if you can provide a minimal reproducible example, because this error look somewhat generic

@kumarav16
Copy link
Author

Hi @kravets-levko Kindly find the answer to the above questions below:

  • do you see this error with latest version of the library? We have not yet tried with the latest version which is 1.8.4, we are getting the error with version 1.7.1

  • do you use proxy? No proxy has been used

  • on which stage (opening session, running query, getting the result, etc.) this is happening? while running a query

  • how large is your result set? max 600-700 KB

@DevPro1993
Copy link

Is this issue resolved? I am also getting the same issue. On local it is working fine but when I deploy my code to lambda, I am getting this error.

@kumarav16
Copy link
Author

Hi @kravets-levko, hope you are doing well!
could you please suggest solution for the above issues as still we are facing the same issues while running longevity test.

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

3 participants