#community-help

Typesense Cloud Instance Timeout Issue

TLDR Ken experienced timeouts during an upsert process. Kishore Nallan resolved the issue by fixing a disk problem and recommended upgrading to version 0.24.1.

4mo

Join the chat

May 16, 2023 (4 months ago)

Photo of md5-e647a31295419f1362630a69cf274ae3

Ken

12:39 PM

👋 Hello Typesense team! I’m looking for some support with out Typesense cloud instance ----->

12:39

Ken

12:39 PM

We have a process that runs every few hours that does a jsonl upsert of ~300k documents. It has been running fine for months, but as of today it started timing out.

12:39

Ken

12:39 PM

There hasn’t been any big change to our data or process that would explain this. We tested with a small number of documents (40) and it took a lot longer than expected. Wondering what your advice is to address this.

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

12:39 PM

Please DM me your cluster ID

Ken

12:39 PM

My first thought was to drop/recreate the schema and re-run the upsert process (we do this periodically anyway when there has been a bigger change to our dataset). Any thoughts?

12:40

Ken

12:40 PM

done!

12:42

Ken

12:42 PM

I believe we are currently running 0.24.0.rcn28

Kishore Nallan

12:43 PM

Checking

12:44

Kishore Nallan

12:44 PM

Somehow the write queue on this node is stuck. I can try restarting the Typesense process to see if it helps. It will require a few mins of downtime. Shall I proceed?

Ken

12:45 PM

yes, please go ahead

Kishore Nallan

12:46 PM

Also, for what particular feature did you switch to the RC build?

Ken

12:47 PM

Trying to recall b/c it’s been a few months. I think it had to do with a newer filter or sort option.

12:48

Ken

12:48 PM

Like how null values are ranked in results

Kishore Nallan

12:51 PM

Ah I see that your instance had a disk issue. This is now fixed and Typesense is starting back up.

Ken

12:53 PM

Great, thank you! I can see that our searches are running fine…

12:53

Ken

12:53 PM

I will try manually initiating the upsert

Kishore Nallan

12:54 PM

I recommend upgrading to the last stable version 0.24.1 --> I think there is a fix for this particular issue that this build suffers from.

Ken

01:09 PM

OK, makes sense. I will run some local tests against the docker image for 0.24.1 and if everything looks good we’ll schedule an upgrade.

01:10

Ken

01:10 PM

BTW, our upsert completed fine in 123 seconds (consistent with past performance)

Kishore Nallan

01:10 PM

👍

Ken

01:11 PM

Thank you for the (as usual) excellent support!

Typesense

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

Indexed 2776 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Troubleshooting Write Timeouts in Typesense with Large CSVs

Agustin had issues with Typesense getting write timeouts while loading large CSV files. Kishore Nallan suggested chunking data or converting to JSONL before loading. Through troubleshooting, they identified a possible network problem at AWS and found a workaround.

29mo

Troubleshooting Indexing Duration in Typesense Import

Alan asked about lengthy indexing times for importing documents to Typesense. Jason suggested various potential causes, including network connectivity and system resources. They later identified the problem to be an error in Alan's code.

12mo

Handling Kinesis Stream Event Batching with Typesense

Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.

22mo

Bulk Import 50MB JSON Files Error - Timeout and Solutions

madhweep encounters an error while bulk importing JSON files. Kishore Nallan provided help, but the issue persists. Jason intervenes and after troubleshooting, they concluded the cluster had run out of memory causing the issue. The problem was resolved by using a cluster with sufficient memory. Daniel also experienced a similar issue, resolved by increasing the timeout.

24mo

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.

12mo