Thanks for the reply Shawn, i certainly would not want to request a change
to solr code to support H2, for my needs. I'll leave that up to the Solr
team. :) as i don't see H/2 being a real improvement for something like
solr.
On Mon, Feb 26, 2018 at 10:29 AM, Shawn Heisey wrote:
> On 2/23/2018
On 2/23/2018 1:28 PM, Jeff Dyke wrote:
> Answering a bit of my own question, the underlying jetty would have to be
> built with it, and get pushed into its jar directory.
>
> I think i'll put nginx in front of this, do a quick proxy forcing 1.1 and
> move on, but if anyone knows any tricks, it'll b
Answering a bit of my own question, the underlying jetty would have to be
built with it, and get pushed into its jar directory.
I think i'll put nginx in front of this, do a quick proxy forcing 1.1 and
move on, but if anyone knows any tricks, it'll be good just for
thoroughness of this thread and
Thanks for the tip Jason. I didn't see the -j option there or here
https://lucene.apache.org/solr/guide/7_2/solr-control-script-reference.html
I'll keep this short, i tried to add it to the init.d script and then
interacting directly with the solr binary, but ultimately saw that
logs/solr-console
Hi Jeff,
I haven't tested your exact use case regarding H/2, but the "bin/solr"
startup script has a special "-j" options that can be used to pass
arbitrary flags to the underlying Jetty server. If you have options
that work with vanilla Jetty, they _should_ work when passed through
the "bin/solr
