Understanding Indexing and Cloning in Typesense
TLDR Calum learned about immediate indexing in Typesense and the new feature of index cloning from Jason.
1
Oct 14, 2022 (14 months ago)
Calum
10:36 PMJason
10:38 PMThat said, when running in HA clustered mode, each node is eventually consistent, so there will be a few seconds delay from a 200 and when the data shows up in search on each node, depending on the network latency between the nodes
1
Calum
11:01 PMCalum
11:02 PMJason
11:07 PMOct 15, 2022 (14 months ago)
Calum
01:09 PMJason
01:10 PMCalum
01:10 PMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Document Import Error
Christopher had trouble importing 2.1M documents into Typesense due to memory errors. Jason clarified the system requirements, explaining the correlation between RAM and dataset size, and ways to tackle the issue. They both also discussed database-like query options.
Improving Typesense Query Performance
Jonathan queried about slower than expected typesense query performance. Jason and Kishore Nallan offered solutions and explanations. After a series of tests, Jonathan found other queries returned results quickly, indicating the issue was specific to the original query.
Optimizing Typesense Implementation for Large Collections
Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.
Revisiting Typesense for Efficient DB Indexing and Querying
kopach experienced slow indexing and crashes with Typesense. The community suggested to use batch import and check the server's resources. Improvements were made but additional support was needed for special characters and multi-search queries.
Addressing Typesense Server Issues and Optimization Needs
Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.