Any way to change thread-pool-size after the serve...
# community-help
r
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.
j
IIRC
thread-pool-size
can only be changed at startup… But just in case, could you try this:
Copy code
curl "<http://localhost:8108/config>" \
        -X POST \
        -H 'Content-Type: application/json' \
        -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
        -d '{"thread-pool-size": 240}'
r
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.
This particular instance by the way always has '1' queued_write, it's like forever stuck.
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.
🙏 1
j
Hmmm, that does sound like a bug…