#community-help

Troubleshooting Create Index Issue on Typesense Instance

TLDR John was having issues creating new indices on a Typesense instance which Jason suggested could be due to old bugs or heavy search queries monopolizing CPU. After a restart, the issue was resolved. Jason also recommended upgrading the Typesense version.

3mo

Join the chat

Sep 02, 2023 (3 months ago)

Photo of md5-21545f1facb7836c149bc4c70752bd2b

John

04:52 PM

Hmm, seems like we can't create new indices on one of our Typesense instances anymore. It just times out, even with a small schema and a high timeout, whereas the same schema is instantly created on our other instances. There's nothing out of the ordinary about this instance, CPU and memory usage looks fine, logs look normal. Any idea what might be going on?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:56 PM

Could you DM me your cluster ID?

John

05:00 PM

Ah sorry for not being clear, we're running it ourselves

Jason

05:01 PM

Are the logs periodically outputting the latest sequence numbers?

05:02

Jason

05:02 PM

Also, in earlier versions of Typesense (before 0.25.0) there were some missing validation bugs that would cause bad data to get into the write queue and freeze it

05:03

Jason

05:03 PM

Could you post the last say 50 lines from the logs?

John

05:05 PM

Sure, here's a sample: https://pastebin.com/tPxQri3e

05:06

John

05:06 PM

> Also, in earlier versions of Typesense (before 0.25.0) there were some missing validation bugs that would cause bad data to get into the write queue and freeze it
Interesting, we've been running 0.25.0.rc25 for a while, maybe fixed after that?

Jason

05:07 PM

Yeah... I would recommend upgrading to 0.25.1.rc6

05:08

Jason

05:08 PM

Although, this doesn't look like a write stall issue. There's potentially a set of heavy search queries that are monopolizing CPU... Notice how pending_queue_size is reducing very slowly

05:09

Jason

05:09 PM

Restarting would help flush that queue. We've also added safeguards to time-out stale search queries stuck in the queue for too long in recent builds

John

05:10 PM

CPU usage was at almost 0, but maybe something's still stuck. I restarted it now, let's see if that helps

05:15

John

05:15 PM

Now schema creation works again. Will look into upgrading ASAP and hope it doesn't happen again

Thanks for the help!

Typesense

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

Indexed 3005 threads (79% resolved)

Join Our Community

Similar Threads

Addressing Typesense Server Issues and Optimization Needs

Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.

14mo

Revisiting Typesense for Efficient DB Indexing and Querying

kopach experienced slow indexing and crashes with Typesense. The community suggested to use batch import and check the server's resources. Improvements were made but additional support was needed for special characters and multi-search queries.

9mo

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

Troubleshooting 400 Error When Upgrading Typesense Firestore Extension

Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.

14mo

Troubleshooting Stalled Writes in TypeSense Instance

Robert was experiencing typesense instances getting stuck after trying to import documents. Kishore Nallan provided suggestions and added specific logs to diagnose the issue. The two identified queries causing troubles but the issues had not been fully resolved yet.

12mo