#community-help

Updating Collection Schema on Typesense Cloud Returns 408 Error

TLDR 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

Join the chat

Jul 26, 2023 (4 months ago)

Photo of md5-153deb374053266af0ef241c0c4ac510

Rushil

12:17 AM

I am trying to update a collection schema on Typesense cloud and keep getting a 408 error with an empty body. Any ideas what might be happening? Here is my update schema:

{
  "fields": [
    {
      "name": "geoloc",
      "drop": true
    },
    {
      "name": "_geoloc",
      "type": "geopoint[]",
      "optional": true
    }
  ]
}

12:18

Rushil

12:18 AM

It seems that our cluster got updated to 0.25.0.rc55 in the interim - not sure if that is causing problems

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

12:25 AM

Rushil I sent you an email with more context about the upgrade, about an hour ago.

We do not upgrade Typesense versions, except when a cluster runs into a bug that could be fixed by a more recent RC build.

This particular schema change payload caused an issue in 0.24.1 and so we upgraded your cluster to 0.25.0.rc55, which stabilized the cluster, but it looks like another variation of this issue still exists in this RC build as well.

We’ll take a closer look into this shortly.

12:26

Jason

12:26 AM

We’ll recover your cluster manually for now… in the meantime, I’d recommend avoiding doing this schema change. And instead creating a new collection with the updated schema and reindex your data in it

12:26

Jason

12:26 AM

I’ll keep you posted on the patch for the root cause of the issue

Rushil

12:28 AM

Jason I actually tried deleting the collection, but that timed out as well. I ended up trying to reprovision with more RAM

Jason

12:28 AM

Looks like the cluster is in a state that prevents any API actions

12:29

Jason

12:29 AM

Should be back up in about 5 mins, and you should be able to increase RAM on the same cluster

12:36

Jason

12:36 AM

The cluster is stable now… The upgrade is going through now

Rushil

12:38 AM

Attempting to delete the collection now

12:39

Rushil

12:39 AM

Sweet! That seemed to go through

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

Issues with Typesense API: RAM Upgrade and Error 422

Laura encountered Error 422 while submitting products to typesense. Jason suggested checking the response body, upgrading RAM, and checking for schema issues. Error resolved after upgrading RAM.

6mo

Unexpected Schema Updates in Typesense Cloud

Samuel encountered unexpected schema updates in Typesense Cloud, which they didn't make. Jason asked for more information to investigate the issue.

9mo

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

Issues and solutions regarding Typesense Updates

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

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.

11mo