Typesense Server Error on GCP Kubernetes
TLDR Atul encountered an error while using Typesense on GCP Kubernetes. Kishore Nallan suggested checking server logs for clues.
Powered by Struct AI
3
3mo
Jun 21, 2023 (3 months ago)
Atul
Atul
11:25 AMtyesense service is hosted on gcp kubernetes every time i refresh the typesense getting this error
Request #1687346469637: Request to Node 0 failed due to "ERR_REQUEST_ABORTED error request aborted"
Request #1687346469637: Sleeping for 0.1s and then retrying request...
whats wrong ?
Request #1687346469637: Request to Node 0 failed due to "ERR_REQUEST_ABORTED error request aborted"
Request #1687346469637: Sleeping for 0.1s and then retrying request...
whats wrong ?
11:33
Atul
11:33 AMServerError: Request failed with HTTP code 502
at ServerError.TypesenseError [as constructor] (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28)
at new ServerError (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/ServerError.js:25:42)
at ApiCall.customErrorForResponse (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:347:21)
at /Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:204:58
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:33:23)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:18:139)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at fulfilled (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:5:58)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
httpStatus: 502
}
ServerError: Request failed with HTTP code 502
at ServerError.TypesenseError [as constructor] (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28)
at new ServerError (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/ServerError.js:25:42)
at ApiCall.customErrorForResponse (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:347:21)
at /Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:204:58
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:33:23)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:18:139)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at fulfilled (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:5:58)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
httpStatus: 502
}
at ServerError.TypesenseError [as constructor] (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28)
at new ServerError (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/ServerError.js:25:42)
at ApiCall.customErrorForResponse (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:347:21)
at /Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:204:58
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:33:23)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:18:139)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at fulfilled (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:5:58)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
httpStatus: 502
}
ServerError: Request failed with HTTP code 502
at ServerError.TypesenseError [as constructor] (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28)
at new ServerError (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/Errors/ServerError.js:25:42)
at ApiCall.customErrorForResponse (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:347:21)
at /Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:204:58
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:33:23)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at step (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:18:139)
at Object.next (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
at fulfilled (/Users/atulsingh/Desktop/Work/typesense/node_modules/typesense/lib/Typesense/ApiCall.js:5:58)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
httpStatus: 502
}
Kishore Nallan
Kishore Nallan
12:09 PMCheck the Typesense server logs, that might offer a hint.
Typesense
Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI
Indexed 2764 threads (79% resolved)
Similar Threads
Resolving Kubernetes Error in Typesense
Pavan experienced issues with Typesense on Kubernetes. Kishore Nallan advised to run Typesense as a single pod to recover.

5
12mo
Solved
Troubleshooting Typesense Cloud Server Request Problem
Isaac reported an issue with their Typesense cloud server. Jason advised replicating the problem in curl and sharing the curl command for further help.
3
9mo
Resolving Typesense API "Not Ready or Lagging" Error in Kubernetes
Hariharan is experiencing "Not ready or lagging" error with Typesense API in Kubernetes. Jason suggests using bulk import and exponential backoff, but the issue persists.
5
7mo