Typesense Import Issue with HTTP Code 503 Error
TLDR Tomas faced errors while importing to typesense, including an HTTP code 503. Jason identified the issue as CPU exhaustion and recommended slowing down writes or upgrading to at least 4vCPU.
1
1
May 24, 2023 (6 months ago)
Tomas
06:27 PMTrying to import to typesense, I had the error
Request failed with HTTP code 503 | Server said: Not Ready or Lagging
and when I check the cluster, only has 3k of 19k records.Now, when I do the request to the schema information, I see that there are 3125 contacts, but if I use a
filterBy
, I see around 9k records.I tried to import again, and it doesn’t throw errors, but I have the same amount of records.
Did I broke the cluster? Is there a way to solve it?
Thank you!Hello!
Trying to import to typesense, I had the error
Request failed with HTTP code 503 | Server said: Not Ready or Lagging
and when I check the cluster, only has 3k of 19k records.Now, when I do the request to the schema information, I see that there are 3125 contacts, but if I use a
filterBy
, I see around 9k records.I tried to import again, and it doesn’t throw errors, but I have the same amount of records.
Did I broke the cluster? Is there a way to solve it?
Thank you!
Jason
06:49 PMJason
06:51 PMJason
06:52 PMJason
06:52 PMThis happens temporarily as the documents in the write queue are processed
Tomas
07:27 PMJason
07:58 PMJason
07:58 PMTomas
09:45 PMMay 25, 2023 (6 months ago)
Jason
01:52 AM1
Tomas
04:44 PM1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
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.
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.
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.
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.
Improving Record Retrieval Speed from Typesense
Yoshi sought ways to accelerate Typesense record retrieval. Jason advised upgrading to high availability and using the documents/export endpoint. They also noted a high volume of writes consuming significant CPU capacity as a possible performance factor.