-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
connectionTimeoutSeconds seems to not be working #174
Comments
Setting the timeout to 1 Seems to be working for deleting a collection.
|
@ivanbacher As of Other endpoints like delete still use the timeout setting. |
Ah super. thanks for the info. I still get this error though when doing a bulk import
Now I have double the data in the This only occurs on the VM I am running typesense on (2 cpus). If I run the same code on my local machine (macbook pro) then there is no error |
It's possible that CPU is being saturated... Could you try on a 4 core machine? |
Tried with a 4 core machine and still getting the same error |
Could you share about 100 lines from the Typesense logs around the time when the socket hang happens? |
Description
Init client and set
connectionTimeoutSeconds
to 10. Create a bulk data import. Time this using node.js timers.No timeout error or warning
Steps to reproduce
output:
Expected Behavior
Raise timeout error
Actual Behavior
No timeout error or warning
Metadata
Typesense Version: 0.25.1
OS: Docker Container running on MacOs
The text was updated successfully, but these errors were encountered: