Hi, we’re using the NodeJS bindings for typesense,...
# community-helpt
Todd Tarsi
10/20/2022, 9:35 PMHi, 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:
Copy code
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”
```j
Jason Bosco
10/21/2022, 12:34 AMYou can configure this using this parameter when instantiating the client: https://github.com/typesense/typesense-js/blob/95ef925ed0de714f10074027d0c1c8929a11a5a2/src/Typesense/Configuration.ts#L76
t
Todd Tarsi
10/21/2022, 5:30 PM@Jason Bosco - If your default is 5, why is it timing out at 2 seconds?
Todd Tarsi
10/21/2022, 5:32 PMIs there an environment variable it might be reading from? We don’t pass any timeout options into our constructor
j
Jason Bosco
10/21/2022, 5:36 PMDo you use axios directly in your project? If so, I wonder if you have global axios timeout configured which is taking precedence
t
Todd Tarsi
10/21/2022, 5:37 PMnot directly, but perhaps a module (or a module of a module, etc)
Todd Tarsi
10/21/2022, 5:38 PMit looks like we use assembly ai for some transcription related tasks, and they also consume axios?
j
Jason Bosco
10/21/2022, 5:38 PMMay be they’ve configured a global axios timeout?
t
Todd Tarsi
10/21/2022, 5:47 PMScanning their source code, they do not appear to.
Todd Tarsi
10/21/2022, 6:10 PMIt’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
Todd Tarsi
10/21/2022, 6:12 PMThose are the only two packages that ping via
npm lsj
Jason Bosco
10/21/2022, 6:29 PMThis 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
Jason Bosco
10/21/2022, 6:30 PMSo not sure where it’s picking up 2s from - that’s not the default in axios or in typesense-js
4 Views