I have no idea why Hybris would initiate these queries, I'd suggest
you ask them.
As to why they'd lead to memory consumption, they shouldn't as Yonik
said. The sort parameter may be uninverting the _docid_ field into the
JVM memory space, but that should happen immediately as of the first
query.
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
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
Looks like it's some sort of ping (liveness) query, probably from a
load balancer?
Actually, it looks like it's a SolrJ client... here's the code that
sets up that exact query:
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 =false is usually associated with SolrCloud as the
aggregator node sends out a sub-request to one replica of each
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