Resolving Typesense API "Not Ready or Lagging" Error in Kubernetes
TLDR Hariharan is experiencing "Not ready or lagging" error with Typesense API in Kubernetes. Jason suggests using bulk import and exponential backoff, but the issue persists.
Feb 22, 2023 (8 months ago)
Hariharan
04:48 AMJason
04:49 AMSee “Handling HTTP 503s”
Feb 23, 2023 (7 months ago)
Hariharan
02:45 AMJason
02:55 AMHariharan
09:09 AMTypesense
Indexed 2786 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Issues in Kubectl v1.26
Arnob and Rubai face issues with Typesense erasing data. Jason and Kishore Nallan suggest HA setup and persistent volume usage. Sai recommends the Typesense Kubernetes operator but Arnob experiences new errors.
Using Typesense in Docker Container – Importing JSONL File
Hakim faced 'Empty reply from server' error when importing a JSONL file into a Typesense-Docker container. Kishore Nallan and Jason suggested checking the docker logs and increasing default RAM and CPU allocation. Finally, Hakim successfully indexed the documents using a PHP script.
Issues deploying Typesense to AWS EKS
Pavan had issues when deploying Typesense to AWS EKS. Kishore Nallan suggested deployment to plain EC2 instances and provided the API key information. Eventually, Pavan resolved the issue with Helm.