Understanding Constant 503 for Typesense Node Instance
TLDR Agustin sought common reasons for receiving a constant 503 for a single node Typesense instance. Kishore Nallan clarified that an explanation would be provided in the server response.
Jun 20, 2021 (27 months ago)
Agustin
07:50 PM Ensured that the server returns a 503 response when it is still catching up on the writes from the leader.Jun 21, 2021 (27 months ago)
Kishore Nallan
01:58 AM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
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.
3Understanding Typesense's High Availability Setup
Imtiaz asked about Typesense's server assignment logic for high availability setup. Jason clarified the round-robin mechanism and advised against client reinitialization. Alex queried about traffic routing to geographically nearest nodes.
1Troubleshooting Typesense Cluster Mode Error Logs
gaurav was having troubles with Typesense error logs in cluster mode. Kishore Nallan explained that it can occur due to master's location troubles and node restarts or state resets, especially in a 3-node setup.