#community-help

Timeout Issues with NodeJS Bindings for Typesense and Axios

TLDR Todd reported intermittent timeout errors when using NodeJS bindings for Typesense with the Axios library. Jason tried to troubleshoot the issue, but the source of the 2s timeout remains unidentified.

14mo

Join the chat

Oct 20, 2022 (14 months ago)

Photo of md5-cccf0b87668408fef09dd77e1948fced

Todd

09:35 PM

Hi, we’re using the NodeJS bindings for typesense, and we’re possibly seeing some timeout issues from the Axios library? We’re getting this message intermittently from our server:


Request #1666300760400: Request to Node 0 failed due to “ECONNABORTED timeout of 2000ms exceeded”

Request #1666300760400: Sleeping for 0.1s and then retrying request...

Request #1666300760512: Request to Node 0 failed due to “ECONNABORTED timeout of 2000ms exceeded”

Request #1666300760512: Sleeping for 0.1s and then retrying request...

Request #1666300760400: Request to Node 0 failed due to “ECONNABORTED timeout of 2000ms exceeded”

Request #1666300760400: Sleeping for 0.1s and then retrying request...

Debug: handler, error
Error: timeout of 2000ms exceeded
at createError (/opt/xyz/node_modules/typesense/node_modules/axios/lib/core/createError.js:16:15)
at RedirectableRequest.handleRequestTimeout (/opt/xyz/node_modules/typesense/node_modules/axios/lib/adapters/http.js:369:16)
at RedirectableRequest.emit (node:events:513:28)
at Timeout.<anonymous> (/opt/xyz/node_modules/follow-redirects/index.js:169:12)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
Debug: internal, error
Error: timeout of 2000ms exceeded
at createError (/opt/xyz/node_modules/typesense/node_modules/axios/lib/core/createError.js:16:15)
at RedirectableRequest.handleRequestTimeout (/opt/xyz/node_modules/typesense/node_modules/axios/lib/adapters/http.js:369:16)
at RedirectableRequest.emit (node:events:513:28)
at Timeout.<anonymous> (/opt/xyz/node_modules/follow-redirects/index.js:169:12)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
Request #1666300760512: Request to Node 0 failed due to “ECONNABORTED timeout of 2000ms exceeded”

```

Oct 21, 2022 (14 months ago)

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

12:34 AM

You can configure this using this parameter when instantiating the client: https://github.com/typesense/typesense-js/blob/95ef925ed0de714f10074027d0c1c8929a11a5a2/src/Typesense/Configuration.ts#L76

Todd

05:30 PM

Jason - If your default is 5, why is it timing out at 2 seconds?

05:32

Todd

05:32 PM

Is there an environment variable it might be reading from? We don’t pass any timeout options into our constructor

Jason

05:36 PM

Do you use axios directly in your project? If so, I wonder if you have global axios timeout configured which is taking precedence

Todd

05:37 PM

not directly, but perhaps a module (or a module of a module, etc)

05:38

Todd

05:38 PM

it looks like we use assembly ai for some transcription related tasks, and they also consume axios?

Jason

05:38 PM

May be they’ve configured a global axios timeout?

Todd

05:47 PM

Scanning their source code, they do not appear to.

06:10

Todd

06:10 PM

It’s a pretty small codebase, 200 lines in total:

https://github.com/PhillipChaffee/assemblyai-node-sdk/blob/master/src/assembly-client.ts

I see 3 invocations of the string timeout, none of which remotely resemble the global timeout stuff

06:12

Todd

06:12 PM

Those are the only two packages that ping via npm ls. I’m pretty stumped by what the source of this could be.

Jason

06:29 PM

This is where we set the axios timeout: https://github.com/typesense/typesense-js/blob/2d20f926dc6e38d802fe8d9c703c0040f5710b9a/src/Typesense/ApiCall.ts#L128

Nothing fancy in there… The axios timeout param is documented here: https://axios-http.com/docs/instance

06:30

Jason

06:30 PM

So not sure where it’s picking up 2s from - that’s not the default in axios or in typesense-js

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Typesense Cloud Requests Timeout Issue

Chase and AK are experiencing timeout issues with Typesense Cloud requests. Jason asked to share more information.

8mo

Debugging "ECONNABORTED Timeout" Issue in Typesense Configuration

GM encountered an "ECONNABORTED timeout" error using their company account with their typesense configuration. Jason is assisting in troubleshooting, suspecting that environment variables might not be set correctly.

14mo

Solving Timeout Error with Typesense in Ruby on Rails

Loic was encountering a timeout error while implementing Typesense with Ruby and Rails. Jason advised to increase the client side connection time. Loic confirmed the solution worked.

18mo

Dealing with Timeout Issues with Typesense in Algolia Plugin

Prime encounters timeout while making a typesense request inside a custom algolia autocomplete plugin. Though recommended solutions were tried, the issue wasn't fully resolved.

2mo

Troubleshooting Indexing Duration in Typesense Import

Alan asked about lengthy indexing times for importing documents to Typesense. Jason suggested various potential causes, including network connectivity and system resources. They later identified the problem to be an error in Alan's code.

15mo