-
Notifications
You must be signed in to change notification settings - Fork 109
Open
Description
To avoid situations where an index gets overloaded with searches (sometimes a slow search can cause this), I implemented an option called "max_search_queue", which sets a limit of the number of threads waiting to acquire the search semaphore in TrafficLimitingSearcher. If this limit is reached, it just rejects the search and throws InterruptedException instead of melting down. I've been running this in production and it seems to work well.
If this sounds good, I'll clean this up into a nice pull request, but here's the main code change:
The option name I chose in the indexengine_config is "max_search_queue".
Metadata
Metadata
Assignees
Labels
No labels