ECONNRESET error on Typesense cloud
TLDR Masahiro was encountering connectivity issues in Typesense cloud, leading to "ECONNRESET" errors. After investigating and providing their cluster ID and endpoint to Jason, it was discovered that they set the wrong protocol in client initialization was wrong. The error was resolved.
1
Apr 21, 2021 (34 months ago)
Masahiro
03:25 PMRequest #1619018557157: Request to Node 0 failed due to "ECONNRESET socket hang up"
Request #1619018557157: Sleeping for 0.1s and then retrying request...
Request #1619018557157: Request to Node 0 failed due to "ECONNRESET socket hang up"
Request #1619018557157: Sleeping for 0.1s and then retrying request...
{ Error: socket hang up
at createHangUpError (_http_client.js:332:15)
at Socket.socketOnEnd (_http_client.js:435:23)
at Socket.emit (events.js:203:15)
at Socket.EventEmitter.emit (domain.js:448:20)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
code: 'ECONNRESET',
I got this error in Typesense cloud, any workarounds??
Thanks!
Jason
03:35 PMJason
03:36 PMJason
03:39 PMMasahiro
09:57 PMgxu1iajypedl2z0tp
Masahiro
09:59 PM• client.collections().create(usersCollection);
• client.collections(‘users’).documents().create(userData)
Masahiro
10:14 PMJason
11:13 PM1
Apr 22, 2021 (34 months ago)
Masahiro
02:30 AMmyCollection = {
'name': 'books',
'fields': [
{'name': 'id', 'type': 'string'},
{'name': 'title', 'type': 'string' },
{'name': 'publication_year', 'type': 'int32' },
],
'default_sorting_field': 'publication_year'
};
try{
await client.collections().create(myCollection);
}catch(e){
console.log(e);
}
Masahiro
02:31 AMRequest #1619058629397: Request to Node 0 failed due to "ENOTFOUND getaddrinfo ENOTFOUND "
Request #1619058629397: Sleeping for 0.1s and then retrying request...
Request #1619058629397: Request to Node 0 failed due to "ENOTFOUND getaddrinfo ENOTFOUND "
Request #1619058629397: Sleeping for 0.1s and then retrying request...
{ Error: getaddrinfo ENOTFOUND
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
errno: 'ENOTFOUND',
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: '',
host: '',
port: '443',
config:
{ url:
'',
method: 'post',
data:
'{"name":"books","fields":[{"name":"id","type":"string"},{"name":"title","type":"string"},{"name":"publication_year","type":"int32"}],"default_sorting_field":"publication_year"}',
headers:
{ Accept: 'application/json, text/plain, */*',
Masahiro
02:35 AMclient initialization was wrong.
not http, https
Jason
02:35 AMJason
02:36 AMtsmguza3k7b4vqh9p
was terminated, so it's not an active clusterMasahiro
03:26 AMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
Resolve Connection Error on Records Upsert
Jainil faced consistent connection errors while upserting records. Jason identified an OOM issue, suggesting a capacity upgrade. Auto-scaling was discussed and the upgrade implementation process, which was in progress, was clarified.
Troubleshooting Typesense Cluster Multi-node Leadership Error
Bill experienced a problem with a new typesense cluster, receiving an error about no leader and health status issues. Jason and Kishore Nallan provided troubleshooting steps and determined it was likely due to a communication issue between nodes. Kishore Nallan identified a potential solution involving resetting the data directory. Following this, Bill reported the error resolved.
Typesense Error in Unit Testing for Python
Mehdi was encountering errors while running unit tests for Typesense functionalities in Python. Through discussion with Kishore Nallan, they recognized resource constraints might be causing the issue during JSONL file import. As suggested by Kishore Nallan, adding a short sleep after the import resolved the problem.
Unresolved High-Volume Write Issue in Typesense
Greg experienced issues with Typesense where it became unresponsive during high-volume write operations. Jason and Kishore Nallan suggested several solutions, but the issue remained unresolved. They suspect that the problem occurs when concurrent writes are happening to the same collection.
Debugging and Recovery of a Stuck Typesense Cluster
Charlie had a wedged staging cluster. Jason provided debugging and recovery steps, and Adrian helped with more insights. It turns out the issue was insufficient disk space. Once Adrian increased the disk size, the cluster healed itself.