[
https://issues.apache.org/jira/browse/SOLR-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166148#comment-17166148
]
Atri Sharma commented on SOLR-13528:
------------------------------------
Hi Varun,
Thanks for your inputs. Here are my responses:
# Yes, the request expiration time is meant for a stable way to expire
requests in the wait queue, but I agree that a hard limit on the size of the
wait queue is needed. I will add it in the PR>
# The rate limiting is being done in SolrDispatchFilter – which AFAIK should
be able to handle all cases of failures since it is the main request entry
point?
> Rate limiting in Solr
> ---------------------
>
> Key: SOLR-13528
> URL: https://issues.apache.org/jira/browse/SOLR-13528
> Project: Solr
> Issue Type: New Feature
> Reporter: Anshum Gupta
> Assignee: Atri Sharma
> Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
> In relation to SOLR-13527, Solr also needs a way to throttle update and
> search requests based on usage metrics. This is the umbrella JIRA for both
> update and search rate limiting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
