#community-help

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.

2mo

Join the chat

Sep 14, 2023 (2 months ago)

Photo of md5-ca6495d5be926db80e09aabf066f4b8b

Michael

05:11 PM

Does the http request for updating a collection leave the connection open over the entire reindexing process? If so, what happens in case of a timeout/connection issue?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

05:15 PM

> Does the http request for updating a collection leave the connection open over the entire reindexing process
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.

Michael

05:40 PM

So if I'm making a schema change, say making an indexed field no longer indexed. If the connection is interrupted, will the collection's configuration settings reflect the old schema or the new one?

Jason

06:31 PM

It will reflect the new one, after it completes executing it fully

06:32

Jason

06:32 PM

On a side note, for the size of your dataset, doing an in-place schema migration might be time-consuming. I would recommend following this approach instead: https://typesense.org/docs/0.25.1/api/collections.html#using-an-alias

07:45 PM

Yes let's do it

Jason

07:59 PM

You're all set

07:59

Jason

07:59 PM

Your cluster should be in a clean slate state now

Michael

08:02 PM

Thanks a lot!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

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.

2mo

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.

23mo

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.

2mo

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.

8mo

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.

10mo