@seanhoots Will it be possible for you to share the dataset with me? And perhaps the query that crashes the server? You can create an issue here: https://github.com/typesense/typesense/issues – I can then take a look to see what’s happening. Based on the stacktrace you have posted though, it seems like it was able to find the document in-memory but not on the disk. I’ve never seen anything like that, but I have not tested extensively on Docker, so it might be a Docker data layering issue.
My answers to your other questions:
- How can I bulk add documents to a collection in one call instead of iterating through a file and making calls one by one
Most of the work for this is already done. Will be adding bulk API in the next release.
- Are there immediate plans to have some UI console as front end to the TypeSense server like the way Algolia works without having to deal with shell commands.
That would be useful, will think about it, but it probably has to be a separate app since we don’t want to mix the concerns.
- What is the recommended server hardware requirement for a typical application with about 3 collections, each having about hundreds of thousand documents and about 10 indexed fields?
Depends on the type of fields indexed and size of the data. Memory requirements will vary based on the underlying indexing data structure used for specific fields.
- What’s the best way to stop and restart the TypeSense server? And is using
curl http://hostaddress:8108/healththe right and only way to check the status of the server?
Docker stop and start should work, what problem are you facing?