#community-help

Understanding Typesense Throttling Parameters

TLDR Nelson queried about Typesense parameters --healthy-read-lag and --healthy-write-lag. Jason explained that these control widespread write operations and ensure read prioritization. They further elaborated on interpreting logs and network request thresholds.

25mo

Join the chat

Oct 13, 2021 (25 months ago)

Photo of md5-04a94d0e1b53117c272637eb497a1540

Nelson

12:31 AM

These parameters what works do they have? Jason --healthy-read-lag and --healthy-write-lag

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

12:33 AM

By default if heavy write operations are sent to Typesense, they are throttled so that reads (searches) are prioritized and not affected.

12:33

Jason

12:33 AM

Those parameters are to help control how much throttling is applied

12:34

Jason

12:34 AM

You want to essentially watch the logs to see if the thresholds are breached as you're writing data, and increase them as needed

Nelson

12:34 AM

By default it is 1000 and 500

Jason

12:35 AM

Yup, that's the number of writes that have been received, but yet to be applied to the index

Nelson

12:35 AM

Is it saying that the server does not receive read or write requests if the number of indexed documents differs from the amount of documents in database?

Jason

12:37 AM

Similar concept, but it's not based on number of documents, it's based on number of writes. For eg: in a batch import, one write can have many number of documents depending on your import code

Nelson

12:37 AM

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Explanation of Typesense's server parameters `--healthy-read-lag` and `--healthy-write-lag`.

Eric asked about the significance of specific server configuration parameters in Typesense. Jason provided a detailed explanation of how these parameters work during data writes and reads.

22mo

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.

8mo

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.

12mo

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.

14mo

Typesense Instance Issues and Solutions on K8s

Richard encountered issues with a typesense instance, including lag, unresponsiveness, and shut downs. Jason provided potential causes and solution, including adjusting configuration settings and clearing data directory. This resolved Richard's issues.

12mo