Re: SOLR 6.1 | Continuous hits coming for unwanted URL pattern
Hi Erick, The queries are getting initiated from HYBRIS which is our front end application server from where indexing happens as well as queries are fired to fetch data from slaves. The question is why would my back end servers on hybris will initiate these queries because back end servers are responsible ONLY for indexing which happens on MASTER. However, these queries are getting fired on SLAVES. Also we are not using SOLR CLOUD. Saurabh -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: SOLR 6.1 | Continuous hits coming for unwanted URL pattern
Hi Yonik, Thanks for your reply. All our hits are coming from SAP HYBRIS SERVER (hosted on tomcat). However, what I am still not sure if what process will initiate these requests. We are not using any hardware load balancer between hybris and SOLR. So may be LBHttpSolrClient is the one making these hits. But the question is under what scenario will these hits be made and why will it always result in 404. Is there a way to figure out where exactly these hits must be getting triggered from? On hybris back end servers only indexing jobs run which queries DB, creates document and push to SOLR. These jobs are scheduled to run in every 3 minutes. However, the queries which we are seeing are actually getting triggered in seconds. So still puzzled to know what process is triggering it and how can we supress it. Also why these queries are getting triggered on other environments except production. Also can you let me know why would this ping type of hits will lead to memory consumption?? Saurabh -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
SOLR 6.1 | Continuous hits coming for unwanted URL pattern
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*=0=_docid_+asc=false=javabin=2 HTTP/1.1" 404 1081 10.131.74.45 - - [26/Sep/2017:15:09:44 +0530] "GET /solr/select?q=*%3A*=0=_docid_+asc=false=javabin=2 HTTP/1.1" 404 1081 10.131.74.45 - - [26/Sep/2017:15:09:49 +0530] "GET /solr/select?q=*%3A*=0=_docid_+asc=false=javabin=2 HTTP/1.1" 404 1081 10.131.74.45 - - [26/Sep/2017:15:09:54 +0530] "GET /solr/select?q=*%3A*=0=_docid_+asc=false=javabin=2 HTTP/1.1" 404 1081 10.131.74.45 - - [26/Sep/2017:15:09:59 +0530] "GET /solr/select?q=*%3A*=0=_docid_+asc=false=javabin=2 HTTP/1.1" 404 1081 10.131.74.45 - - [26/Sep/2017:15:10:04 +0530] "GET /solr/select?q=*%3A*=0=_docid_+asc=false=javabin=2 HTTP/1.1" 404 1081 10.131.74.45 - - [26/Sep/2017:15:10:09 +0530] "GET /solr/select?q=*%3A*=0=_docid_+asc=false=javabin=2 HTTP/1.1" 404 1081 10.131.74.45 - - [26/Sep/2017:15:10:14 +0530] "GET /solr/select?q=*%3A*=0=_docid_+asc=false=javabin=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
