A couple of things:
1> just getting these queries, even with the sort parameter shouldn't
lead to OOMs. Well, to be more correct it should either OOM
immediately or not at all.

2> The &distrib=false is usually associated with SolrCloud as the
aggregator node sends out a sub-request to one replica of each shard.
Or distributed requests are being sent out to a sharded setup (in non
SolrCloud). Are you absolutely sure you don't have some configuration
mismatch?

3> I'm pretty sure this is coming from some external source, there's
no reason I know of that Solr would just do this. Do you have some
monitoring system in place that fires these queries off?

4> when you do find what's firing these, have them turn the sorting
off as it's a waste to sort but return 0 rows.

Best,
Erick

On Tue, Sep 26, 2017 at 3:55 AM, saurabhagrawal
<saurabh.agraw...@gmail.com> wrote:
> Hi,
>
> We are using SOLR 6.1 with hybris. On our production environment the set is
> as follows:
>
> Master for replication using AFTER_COMMIT and 2 slaves which servers the
> query response. The replication was initially set to 60 seconds as we wanted
> latest data on slaves ASAP.
>
> On production environment we have started to see hits coming from all our 8
> hybris servers to SOLR slave servers of following pattern:
>
> 0.131.74.45 - - [26/Sep/2017:15:09:39 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
> 10.131.74.45 - - [26/Sep/2017:15:09:44 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
> 10.131.74.45 - - [26/Sep/2017:15:09:49 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
> 10.131.74.45 - - [26/Sep/2017:15:09:54 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
> 10.131.74.45 - - [26/Sep/2017:15:09:59 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
> 10.131.74.45 - - [26/Sep/2017:15:10:04 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
> 10.131.74.45 - - [26/Sep/2017:15:10:09 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
> 10.131.74.45 - - [26/Sep/2017:15:10:14 +0530] "GET
> /solr/select?q=*%3A*&rows=0&sort=_docid_+asc&distrib=false&wt=javabin&version=2
> HTTP/1.1" 404 1081
>
>
> These URLs are getting triggered from hybris nodes and just getting
> triggered on production. On lower environments, we don't see this URL.
>
> Note: We are using Tomcat 8.5.14 which is hosting SOLR.
>
> Completely puzzled to see this URL and unable to figure out what is
> triggering this URL. As a result of this URL, the memory on slaves goes high
> consistently leading to out of memory eventually.
>
> Any idea of what this URL is and what component must be firing this ?
>
> Thanks in advance,
> Saurabh
>
>
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Reply via email to