[
https://issues.apache.org/jira/browse/SOLR-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229217#comment-14229217
]
Jayson Minard commented on SOLR-4792:
-------------------------------------
I would be willing to shore up. My Solr-undertow to use as a base. It is
simpler, easy to configure, in production at two deployments of high scale
(1500-1600 qps) using less threads and memory than jetty, out performed
efforts of cloudera stack and did not need to break previous deployments by a
war to accomplish this.
My problem with this issue, to repeat what I said before, and others recently
said today... Is that it is half the story, half baked. Without knowing what
to do, it breaks things for no user benefit.
Do you want to review Solr-undertow and provide feedback and I can merge it
over. Without constraints of old params it can be even cleaner.
It is further along than the startup scripts which really are not enough. And
it has more thought into it than this issue appears to have.
> stop shipping a war in 5.0
> --------------------------
>
> Key: SOLR-4792
> URL: https://issues.apache.org/jira/browse/SOLR-4792
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Assignee: Mark Miller
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-4792.patch
>
>
> see the vote on the developer list.
> This is the first step: if we stop shipping a war then we are free to do
> anything we want.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
