Handling 503 Errors and Reducing Cluster Pressure
TLDR Gustavo faced frequent 503 errors despite having ample memory. Jason suggested handling 503s per Typesense documentation and adjusting settings to reduce unnecessary upserts and cluster pressure.
1
Jun 14, 2023 (4 months ago)
Gustavo
10:01 PM503 Not Ready or Lagging for almost all my requests since 2 hours ago. I have almost 2x the memory being used. Isn't that enough?
Jason
10:06 PMGustavo
10:09 PMv601y2x3upjea4tipGustavo
10:10 PM
Jason
10:11 PMHere’s how to handle 503s: https://typesense.org/docs/guide/syncing-data-into-typesense.html#handling-http-503s
Gustavo
10:12 PMJason
10:12 PMconnection_timeout_seconds and retry_interval_seconds to as high as say 10 minutes and 5 minutes eachhttps://github.com/typesense/typesense-python/blob/765c99668bd9832a9dd523405bc54444b980c475/typesense/configuration.py#L39-L41
Gustavo
10:13 PM1
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
Typesense Import Issue with HTTP Code 503 Error
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.
Inquiry and Troubleshooting of Typesense Cloud
Alex is addressing memory usage, import, and bandwidth issues with Typesense Cloud. Jason helped determine the issues and offered solutions, including in-place upgrades and potential use of Cloudflare for security.
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 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.
Resolve Connection Error on Records Upsert
Jainil faced consistent connection errors while upserting records. Jason identified an OOM issue, suggesting a capacity upgrade. Auto-scaling was discussed and the upgrade implementation process, which was in progress, was clarified.