[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jetty-users] Customizing jetty worker threadpool
- From: Hrishikesh Gadre <gadre.solr@xxxxxxxxx>
- Date: Thu, 21 May 2015 16:44:21 -0700
- Delivered-to: firstname.lastname@example.org
Thanks for the feedback. I think QoSFilter is an interesting alternative but I think it does not quite fit the requirement. Let me elaborate my use-case for better understanding.
Every external request typically spawns multiple internal requests for multiple servers (e.g. for scatter/gather queries). Hence it is important to reserve a certain % of thread-pool capacity for internal requests. Without this reservation, it is quite possible that the thread-pool is consumed entirely by external requests - thereby creating a distributed deadlock (since the external request depends upon the result of internal request which can not be processed due to unavailability of threads).Â
After reading the docs, I am not sure if QosFilter will be able to provide this reservation capability out-of-box. i.e. it ensures to pick a higher priority request from the backlog but doesn't prevent the system to occupy the entire thread-pool with low-priority requests.
Is my understanding correct? Also can you please elaborate the threading model used with the jetty continuation?
>>Or use the QoSFilter to setup a higher priority for internal vs external requests. :-)