overload like the other applications I've tested.
Thanks for your time, and sorry for the mistake!
Mike
On Fri, Sep 21, 2012 at 7:19 AM, Mike Gagnon wrote:
> Thanks. If Solr doesn't have any special logic for dealing with
> algorithmic-complexity attack-like overloads, then it s
with simple queries on a 1.2M doc index.
>
> wunder
> Walter Underwood
> Search Guy, Chegg
>
> On Sep 19, 2012, at 8:20 AM, Erik Hatcher wrote:
>
> > How are you triggering an infinite loop in your requests to Solr?
> >
> > Erik
> >
> > On Sep
n/ping
I am running Solr 3.1, which has that bug.
Thanks,
Mike
On Wed, Sep 19, 2012 at 8:20 AM, Erik Hatcher wrote:
> How are you triggering an infinite loop in your requests to Solr?
>
> Erik
>
> On Sep 19, 2012, at 11:12 , Mike Gagnon wrote:
>
> > [ I am sorry f
erent DoS problems in our front-end code."
Perhaps it is these front-end defenses that help Solr survive my workloads?
Thanks!
Mike Gagnon
> Hm, I'm not sure how to approach this. Solr is not alone here - there's
> container like jetty, solr inside it and lucene inside solr.
&
thin 0.6 seconds.
I also ran Solr+Jetty with non-overload requests coming in 65 requests per
second (overload requests remain at 60 requests per second). In this
workload, the completion rate drops to 15% and the 95th percentile latency
increases to 25.
Cheers,
Mike Gagnon
thin 0.6 seconds.
I also ran Solr+Jetty with non-overload requests coming in 65 requests per
second (overload requests remain at 60 requests per second). In this
workload, the completion rate drops to 15% and the 95th percentile latency
increases to 25.
Cheers,
Mike Gagnon
