#community-help

Issues and solutions regarding Typesense Updates

TLDR Yoshi faced issue in updating a field in Typesense. Jason communicated this as being due to a blocking operation by in-place schema migration and recommended using the alias method.

1mo

Join the chat

Oct 12, 2023 (1 month ago)

Photo of md5-9e27fed7af6568f2c8abff36e7e9da4d

Yoshi

06:25 PM

Hey all, I just tried to update a field on my collection in order to change it to sort: true, but having done so seems to have crashed Typesense. Latency is way up, and is always times out. Monitoring says it’s still healthy though…

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

06:27 PM

Doing an in-place schema migration is a blocking operation... So all reads / writes will be blocked until the operation is complete

06:28

Jason

06:28 PM

We've improved this in the upcoming version of Typesense (v0.26) so it only blocks writes

06:28

Jason

06:28 PM

Until then, I'd recommend using the alias method to change the collection schema in a zero downtime way

06:28

Jason

06:28 PM

https://typesense.org/docs/0.25.1/api/collections.html#using-an-alias

06:29

Jason

06:29 PM

For the issue at hand, I can confirm that the nodes are still executing the alter command

Yoshi

06:29 PM

I see…ok. How long does this operation generally take to complete for a collection of ~900k elements?

06:29

Yoshi

06:29 PM

And do you have a general target of when 0.26 will be released?

Jason

06:32 PM

Looks like each round of modification takes about 20 minutes for your dataset, and I see multiple alters running one after another

06:33

Jason

06:33 PM

We're probably at least two months out from a 0.26 GA release... But we have users using the RC builds in production already. Although the latest RC build has a known performance regression when using group_by. We're working on addressing that, but otherwise it's useable

06:34

Jason

06:34 PM

The alter seems to have completed now

Yoshi

06:34 PM

Cool, seeing data come through again. Sincerely appreciate the fast responses and detailed answers, thank you

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

Updating Collection Schema on Typesense Cloud Returns 408 Error

Rushil had issues updating a schema on Typesense Cloud, receiving a 408 error. Jason assisted, indicating that his cluster upgrade caused the issue, solved it, and advised to avoid similar changes in the future.

4mo

Infix Searching and Schema Updates in Typesense

Loic queried the inability to perform infix searches and update schemas in Typesense. Jason explained that default is prefix search, provided solutions for infix searching, and mentioned that a forthcoming version supports field definition updates. An upgrade was queued from backend.

19mo

Updating "sort" Property in Typesense Collection

toufiq needed to update the schema in an existing Typesense collection to include "sort" property. Jason suggested using aliasing for production environment.

1mo

Fixing Errors on Typesense Cluster

Tugay is having issues with their Typesense cluster, and Jason is trying to diagnose the problem. They have ruled out issues with the data dir and are currently considering whether the errors could be due to high concurrent writes or running bulk migrations. They plan to test with 0.24.0.rcn56 Typesense version.

11mo