[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585174#comment-14585174
]
Mark Miller commented on SOLR-7344:
-----------------------------------
To expand on my concern for new requests with the wrong type:
I know in general, it's not the largest issue currently - if all HttpClients
under SolrDispatchFilter have internal as a default and forwarding is minimal
like it is now, perhaps a simple default in SolrDispatchFiter serves us well. I
think the problem is that this is tricky stuff and will evolve over time and we
don't have an easy way to ensure devs that don't understand this part of the
system don't add code that is not compliant in the future and cause random
deadlocks and/or other hard to debug or notice issues. This is a common
occurrence (devs changing/adding code without knowing all the ramifications),
so for tricky areas like this, I prefer sticking things right in the devs face
with docs and forced params.
> Allow Jetty thread pool limits while still avoiding distributed deadlock.
> -------------------------------------------------------------------------
>
> Key: SOLR-7344
> URL: https://issues.apache.org/jira/browse/SOLR-7344
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Attachments: SOLR-7344.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
