Resolving PAYLOAD_TOO_LARGE Error on Self-Hosted Typesense Server
TLDR Dhruvil is receiving a PAYLOAD_TOO_LARGE error while using the indexing multiple documents API on a self-hosted Typesense server. Kishore Nallan suggests checking if there is another server in front of Typesense, as the error appears to not originate from Typesense.
Oct 10, 2023 (1 month ago)
Dhruvil
05:52 AMI'm getting below error when I'm using indexing multiple documents API.
2023-10-10 11:11:14.516 Response 413 PAYLOAD_TOO_LARGE
org.springframework.web.client.HttpClientErrorException: 413 Request Entity Too Large: "<html><EOL><EOL><head><title>413 Request Entity Too Large</title></head><EOL>
at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:145)
What is the solution for this and how can I increase Payload size for self hosted typesense server?
Kishore Nallan
06:14 AM
Typesense
Indexed 3015 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.
Resolving Typesense v0.22.0 Import Issues
Anton encountered issues importing documents in batches using Typesense v0.22.0. Kishore Nallan suggested using atomic import and proposed a debug build. After multiple trials, they were able to reproduce and fix the issue. Anton confirmed the solution was working.
Addressing Typesense Server Issues and Optimization Needs
Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.