[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463010#comment-16463010
]
Mark Miller commented on SOLR-7344:
-----------------------------------
Heh, it's a serious statement and question.
We do want to determine what the best underlying tech to use is for the long
term and that was part of the motivation to move away from a WAR (but just
part).
If people like or want Netty, it would be good to know why and get those
discussions out of the way. Personally, I've never used Netty. From what I
understand, it's a lower level project and it would be a lot of work to switch
- so to even consider it, we would want powerful reasons.
AFAIK, the Jetty team has done a ton of work in response to the popularity of
frameworks like Netty to match most of there features. Perhaps not as light
weight in some cases, but that is just because if you are building it for your
app, you might be able to leave a lot out. I'm not very optimistic we could
leave much out of what Jetty does for us. Instead, we would need to take a long
time to stabilize.
So my thoughts have been to work towards supporting more advanced features
available in Jetty over time.
> 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
> Priority: Major
> Attachments: SOLR-7344.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
