Re: jetty.xml

k could still get done. This is just an idea, not a > suggestion. > > -Original Message- > From: Shawn Heisey [mailto:apa...@elyograg.org] > Sent: Wednesday, August 19, 2015 9:15 AM > To: solr-user@lucene.apache.org > Subject: Re: jetty.xml > > On 8/18/2015 11:

RE: jetty.xml

done. This is just an idea, not a suggestion. -Original Message- From: Shawn Heisey [mailto:apa...@elyograg.org] Sent: Wednesday, August 19, 2015 9:15 AM To: solr-user@lucene.apache.org Subject: Re: jetty.xml On 8/18/2015 11:50 PM, William Bell wrote: > We sometimes get a spike in S

Re: jetty.xml

On 8/18/2015 11:50 PM, William Bell wrote: > We sometimes get a spike in Solr, and we get like 3K of threads and then > timeouts... > > In Solr 5.2.1 the defult jetty settings is kinda crazy for threads - since > the value is HIGH! > > What do others recommend? The setting of 1 is so that th

jetty.xml

We sometimes get a spike in Solr, and we get like 3K of threads and then timeouts... In Solr 5.2.1 the defult jetty settings is kinda crazy for threads - since the value is HIGH! What do others recommend? Fusion jetty settings for Threads: * * false T

Re: Negatives of binding multiple ports in jetty.xml?

10, 2015, at 03:18 PM, eirik wrote: > Hi, > > I have not experienced any negatives with having more than 1 > "addConnector" > (using bio.SocketConnector) specified in jetty.xml. e.g 8983, 8984, 8985 > etc > Without knowing to much of whats going on in the backgro

Re: usage of /etc/jetty.xml when debugging Solr in Eclipse

yes, I am using https://github.com/alexwinston/RunJettyRun that apparently is a fork of the original project that originated in the need to use an jetty.xml. So I am already setting an additional jetty.xml, this can be done in the Run configuration, no need to use -D param. But as I mentioned

Re: usage of /etc/jetty.xml when debugging Solr in Eclipse

Hi, run-jetty-run issue #9: ... In the VM Arguments of your launch configuration set -Drjrxml=./jetty.xml If jetty.xml is in the root of your project it will be used (you can also use a fully qualified path name). The UI port, context and WebApp dir are ignored, since you can define them in

usage of /etc/jetty.xml when debugging Solr in Eclipse

Hi, I am following http://www.lucidimagination.com/devzone/technical-articles/setting-apache-solr-eclipse in order to be able to debug Solr in eclipse. I got it working fine. Now, I usually use ./etc/jetty.xml to set logging configuration. When starting jetty in eclipse I dont see any log files

Re: performace jetty (jetty.xml)

Lucene - Nutch > Lucene ecosystem search :: http://search-lucene.com/ > > -- > *From:* Gastone Penzo > *To:* solr-user@lucene.apache.org; d...@lucene.apache.org > *Sent:* Tuesday, October 18, 2011 10:03 AM > *Subject:* performace jetty (jetty.xml) > >

Re: performace jetty (jetty.xml)

/ > >From: Gastone Penzo >To: solr-user@lucene.apache.org; d...@lucene.apache.org >Sent: Tuesday, October 18, 2011 10:03 AM >Subject: performace jetty (jetty.xml) > > >Hi, >i just change my solr installation from 1.4 to 3.4.. >i can notice that

Re: performace jetty (jetty.xml)

jetty configuration file (jetty.xml) is changed. > default threads number is higher, theadpool is higher > and other default value are higher. is it normal?? > > what number of these value do you seems are correct for me? > i have a dedicated machine with 2 solr istances inside >

performace jetty (jetty.xml)

Hi, i just change my solr installation from 1.4 to 3.4.. i can notice that also jetty configuration file (jetty.xml) is changed. default threads number is higher, theadpool is higher and other default value are higher. is it normal?? what number of these value do you seems are correct for me? i