#community-help

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.

14mo

Join the chat

Oct 19, 2022 (14 months ago)

Photo of md5-6384d24e1825271b2c37ad8afa24a899

Robert

10:03 PM

Any way to change thread-pool-size after the server is running? Turns out 32 threads isn't enough and I need to bump it way up. Was hoping to avoid stopping/starting server as it takes about 2 hours to cycle.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

10:05 PM

IIRC thread-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 PM

thanks. The curl config call is just hanging, doesn't look like it's gonna return. Probably because typesense is pegging the 32 CPUs at100%. I think I'll have to bring search and typsense down and back up again. No worries.

10:38

Robert

10:38 PM

This particular instance by the way always has '1' queued_write, it's like forever stuck.

10:40

Robert

10:40 PM

I think I know the set of document inserts that caused it. Once I get the production server fixed and put out all the fires I plan on spending some time figuring out which document causes the stuck queued write and submit a bug about it if I discover a problem.

Jason

11:02 PM

Hmmm, that does sound like a bug…

Typesense

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

Indexed 3005 threads (79% resolved)

Join Our Community

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.

14mo

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.

14mo

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.

10mo