Daniel,
Is it worth saying that you have honkin' long queries and there must be a
simpler way? ( I am a big fan of KISS . . Keep It Simple Stupid). I am not
calling you names, just saying that this acronym comes up in just about every
project I work on. It is akin to the Peter Principle, where
If you are able to draw gc logs in gcviewer when OOM happens, it can give
you idea if it was sudden OOM or heap gets filled over a period of time.
This may help to nail down if any particular query is causing the problem
or something else...
Thanks,
Susheel
On Sat, May 27, 2017 at 5:36 PM, Daniel
Thanks for the support so far.
I am going to analyze the logs in order to check the frequency of such
queries. BTW, I have forgot to mention, the soft and the hard commits are
each 60 sec.
BR
Daniel
Am 27.05.2017 22:57 schrieb "Erik Hatcher" :
> Another technique to consider is {!join}. Index t
Another technique to consider is {!join}. Index the cross ref id "sets" to
another core and use a short and sweet join, if there are stable sets of id's.
Erik
> On May 27, 2017, at 11:39, Alexandre Rafalovitch wrote:
>
> On top of Shawn's analysis, I am also wondering how often those FQ
>
On top of Shawn's analysis, I am also wondering how often those FQ
queries are reused. Because they and the matching documents are
getting cached, so there might be quite a bit of space taken with that
too.
Regards,
Alex.
http://www.solr-start.com/ - Resources for Solr users, new and expe
On 5/27/2017 9:05 AM, Shawn Heisey wrote:
> On 5/27/2017 7:14 AM, Daniel Angelov wrote:
>> I would like to ask, what could be the memory/cpu impact, if the fq
>> parameter in many of the queries is a long string (fq={!terms
>> f=...}..., ) around 200 chars. Most of the queries are like:
>>
On 5/27/2017 7:14 AM, Daniel Angelov wrote:
> I would like to ask, what could be the memory/cpu impact, if the fq
> parameter in many of the queries is a long string (fq={!terms
> f=...}..., ) around 200 chars. Most of the queries are like:
> "q={!frange l=Timestamp1 u=Timestamp2}... + some
