Handling HTTP Connections during Schema Changes in Typesense
TLDR Michael asked about HTTP request behavior during schema changes and was reassured by Jason that interruption won't stop execution. They finally decided to reset the node to a clean slate.
Sep 14, 2023 (2 months ago)
That's correct. Indexing is a synchronous process in Typesense.
> If so, what happens in case of a timeout/connection issue?
Typesense will still process all the data it has received up until the connection was terminated.
Indexed 3015 threads (79% resolved)
Discussing Migration Handling for TypeSense
Jack asks how to handle "migrations" for TypeSense. Kishore Nallan recommends creating a new collection, reindexing data, then using the alias feature to swap traffic. Further clarification on blocking during schema alteration is provided.
Discussion About Typesense Nodes Not Synchronizing Correctly
Erick experienced an issue where documents weren't updated properly in a Typesense instance running on 3 nodes. Upon requesting debug logs and configs, Jason identified that these nodes weren't part of the same cluster. They couldn't resolve the nodes' failure to connect issue and recommended a fresh installation.
Handling Collection Errors in HA Clusters
Mischa was encountering random collection existence errors when updating schemas in a HA cluster. Jason suggested waiting between deletions and recreations or using an alias for zero downtime switches.
Flushing Queue for Schema Altering in Typesense
Dima experienced repeated schema alterations due to a misconfiguration, causing server timeouts. Kishore Nallan recommended increasing the timeout and adjusting max_retries to resolve the issue.
Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns
Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.