Re: Jetty maxThreads

2017-10-20 Thread Yonik Seeley
The high number of maxThreads is to avoid distributed deadlock. The fix is multiple thread pools, depending on request type: https://issues.apache.org/jira/browse/SOLR-7344 -Yonik On Wed, Oct 18, 2017 at 4:41 PM, Walter Underwood <wun...@wunderwood.org> wrote: > Jetty maxThrea

Re: Jetty maxThreads

2017-10-20 Thread Shawn Heisey
On 10/18/2017 2:41 PM, Walter Underwood wrote: > Jetty maxThreads is set to 10,000 which seams way too big. > > The comment suggests 5X the number of CPUs. We have 36 CPUs, which would mean > 180 threads, which seems more reasonable. I have not seen any evidence that maxThreads at

Re: Jetty maxThreads

2017-10-18 Thread Walter Underwood
alter Underwood <wun...@wunderwood.org> wrote: >> >> Jetty maxThreads is set to 10,000 which seams way too big. >> >> The comment suggests 5X the number of CPUs. We have 36 CPUs, which would >> mean 180 threads, which seems more reasonable. >> >> wunder >> Walter Underwood >> wun...@wunderwood.org >> http://observer.wunderwood.org/ (my blog) >> >> >

Re: Jetty maxThreads

2017-10-18 Thread Walter Underwood
With an 8GB heap, I’d like to keep thread stack memory to 2GB or under, which means a maxThreads of 1000. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Oct 18, 2017, at 1:41 PM, Walter Underwood <wun...@wunderwood.org> wrote: &

Jetty maxThreads

2017-10-18 Thread Walter Underwood
Jetty maxThreads is set to 10,000 which seams way too big. The comment suggests 5X the number of CPUs. We have 36 CPUs, which would mean 180 threads, which seems more reasonable. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog)