[
https://issues.apache.org/jira/browse/SOLR-12405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491602#comment-16491602
]
Mark Miller commented on SOLR-12405:
------------------------------------
We could start simply, but I thought it might be nice to get to the point that
limits could be changed based on changing metrics. If a replica is super
overloaded, we can start queuing up more requests, or even dropping them.
Perhaps this could be complementary to a Jira that I don't think was finished
that lets a replica go inactive when too much load is seen.
> Add a quality of service type filter for request load management and request
> throttling.
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-12405
> URL: https://issues.apache.org/jira/browse/SOLR-12405
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Priority: Major
>
> Trying to manage resource usage just with thread / connection pool limits is
> a losing strategy ( especially without using Continuations and making
> scalability vs performance tradeoffs) if you cannot manage requests.
> A QOSFilter type servlet filter with give us some base functionality we want:
> Ability to limit number of concurrent requests.
> Ability to queue requests without holding a thread per request.
> Ability to drop requests over a certain queue size.
> Ability to prioritize requests on the queue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
