Changing Thread-Pool-Size on a Live Server
TLDR Robert inquired whether it was possible to change thread-pool-size on a live server. Jason suggested a method, but it didn't work. Robert highlighted a potential bug affecting the server performance.
1
Oct 19, 2022 (14 months ago)
Robert
10:03 PMJason
10:05 PMthread-pool-size
can only be changed at startup… But just in case, could you try this:curl "" \
-X POST \
-H 'Content-Type: application/json' \
-H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
-d '{"thread-pool-size": 240}'
Robert
10:10 PMRobert
10:38 PMRobert
10:40 PM1
Jason
11:02 PMTypesense
Indexed 3005 threads (79% resolved)
Similar Threads
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.
Addressing High CPU Usage in Typesense
Robert reported high CPU usage on Typesense, even after halting all incoming searches. Kishore Nallan suggested logging heavy queries and increasing thread count. The issue was resolved after Robert found and truncated unusually large documents in the database.
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.