#community-help

Typesense Cluster Memory Upgrade

TLDR Sruli had a memory issue in their Typesense cluster. Jason suggested upgrading to resolve the issue and helped estimate the necessary RAM upgrade. The solution was successful and the cluster is functioning properly.

10mo

Join the chat

Feb 14, 2023 (10 months ago)

Photo of md5-8c57c435e01337c18bf32b8f7749cabf

Sruli

05:23 PM

Can I query by a field if it isn’t indexed?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

05:24 PM

No, indexing is what makes a field queryable

Sruli

05:24 PM

Gotcha

09:06

Sruli

09:06 PM

Looks like my typesense cluster went down after adding indexing to a certain field, if I upgrade the Ram will I still lose everything?

Jason

09:33 PM

Ah I just saw this, after I DMed you. Your cluster had run out of RAM because of the additional data indexed.

09:33

Jason

09:33 PM

Queued up an upgrade to it

09:34

Jason

09:34 PM

The upgrade just completed. The data should be intact

Sruli

09:34 PM

Looks like I may need to upgrade even higher, or should I wait to see if it goes down?

09:35

Sruli

09:35 PM

It seems to be working but all the stats say it’s high memory usage still

Jason

09:35 PM

Those look at historical data, so if there were any spikes in recent history those alerts will still show up

Sruli

09:35 PM

Okay cool, I will wait a few minutes

Jason

09:36 PM

May I know the total number of records you have and the average size of each record? We can then estimate memory usage and proactively upgrade

Sruli

09:37 PM

It will keep getting bigger and bigger as it’s a library of books, currently it’s just under 1,000 and around 200 pages per book

09:37

Sruli

09:37 PM

We are storing the entire books content so that it can be searched by the contents of it…

09:38

Sruli

09:38 PM

The status now says healthy and I can access the settings for the collections again

09:38

Sruli

09:38 PM

Looks like we are good!

Jason

09:39 PM

Yup. We might have to go to 2GB RAM, but let’s see. Could you index your data now? I can then keep an eye on RAM usage

Sruli

09:42 PM

Ah, the settings got changed somehow and that field got removed…

09:42

Sruli

09:42 PM

That’s why it went back to healthy

09:43

Sruli

09:43 PM

I think we need to upgrade it

09:43

Sruli

09:43 PM

Actually

09:43

Sruli

09:43 PM

It says unhealthy but still works

Jason

09:44 PM

That might be a temporary DNS-caching issue that just affects the health checks UI, since this is a new node

Sruli

09:44 PM

Gotcha

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

Typesense Cloud Cluster Out of Memory Issue

Herman experienced an OUT_OF_MEMORY error after updating their Typesense schema. Jason suggested upgrading to 1GB RAM to accommodate the indexed data.

6mo

Typesense Cloud Cluster Issue and Upgrade Recommendations

Viji reported a cluster issue on Typesense Cloud. Jason identified the cause and recommended upgrading to Typesense 0.24.1 for safeguards against RAM usage spikes.

5mo

Resolving Out of Memory Issue with Cluster

Ed encountered an OUT_OF_MEMORY error while using typesense. Jason suggested increasing the cluster's RAM, accounting for the OS, which resolved the issue.

2mo

Typesense Cluster Upgrade Issues and Solutions

Ken reported a system outage due to Typesense cluster upgrade issues. Jason recommended upgrading to the next RAM tier and explained when the auto upgrade feature takes effect. After a repeat issue, Jason added handling upgrades when disk space ran out to their backlog.

2mo

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.

10mo