bq: ...so I wonder if reducing the heap is going to help or it won’t
matter that much...
Well, if you're hitting OOM errors than you have no _choice_ but to
reduce the heap. Or increase the memory. And you don't have much
physical memory to grow into.
Longer term, reducing the JVM size (assuming
According to the post you linked to, it strongly advises to buy SSDs. I
got in touch with the systems department in my organization and it turns
out that our VM storage is SSD-backed, so I wonder if reducing the heap
is going to help or it won’t matter that much. Of course, there’s
nothing like
The biggest bang for the buck is _probably_ docValues for the fields
you facet on. If that's the culprit, you can also reduce your JVM heap
considerably, as Toke says, leaving this little memory for the OS is
bad. Here's the writeup on why:
http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-
Double check if your queries are not running into deep pagination
(q=*:*...&start=). This is something i recently experienced
and was the only cause of OOM. You may have the gc logs when OOM happened
and drawing it on GC Viewer may give insight how gradual your heap got
filled and run into OOM.
Thanks again.
I’m learning more about Solr in this thread than in my previous months
reading about it!
Moving to Solr Cloud is a possibility we’ve discussed and I guess it
will eventually happen, as the index will grow no matter what.
I’ve already lowered filterCache from 512 to 64 and I’m
On 12/12/2016 3:13 AM, Alfonso Muñoz-Pomer Fuentes wrote:
> I’m writing because in our web application we’re using Solr 5.1.0 and
> currently we’re hosting it on a VM with 32 GB of RAM (of which 30 are
> dedicated to Solr and nothing else is running there). We have four
> cores, that are this size:
...@ebi.ac.uk]
Sent: 12 December 2016 01:31 PM
To: solr-user@lucene.apache.org
Subject: Re: OOMs in Solr
I wasn’t aware of docValues and filterCache policies. We’ll try to fine-tune it
and see if it helps.
Thanks so much for the info!
On 12/12/2016 12:13, Toke Eskildsen wrote:
> On Mon, 2016-12-12 at 10
I wasn’t aware of docValues and filterCache policies. We’ll try to
fine-tune it and see if it helps.
Thanks so much for the info!
On 12/12/2016 12:13, Toke Eskildsen wrote:
On Mon, 2016-12-12 at 10:13 +, Alfonso Muñoz-Pomer Fuentes wrote:
I’m writing because in our web application we’re u
Muñoz-Pomer Fuentes [mailto:amu...@ebi.ac.uk]
Sent: 12 December 2016 10:14 AM
To: solr-user@lucene.apache.org
Subject: OOMs in Solr
Hi Solr users,
I’m writing because in our web application we’re using Solr 5.1.0 and currently
we’re hosting it on a VM with 32 GB of RAM (of which 30 are dedicated to
On Mon, 2016-12-12 at 10:13 +, Alfonso Muñoz-Pomer Fuentes wrote:
> I’m writing because in our web application we’re using Solr 5.1.0
> and currently we’re hosting it on a VM with 32 GB of RAM (of which 30
> are dedicated to Solr and nothing else is running there).
This leaves very little memo
...@ebi.ac.uk]
Sent: 12 December 2016 10:14 AM
To: solr-user@lucene.apache.org
Subject: OOMs in Solr
Hi Solr users,
I’m writing because in our web application we’re using Solr 5.1.0 and currently
we’re hosting it on a VM with 32 GB of RAM (of which 30 are dedicated to Solr
and nothing else is
Hi Solr users,
I’m writing because in our web application we’re using Solr 5.1.0 and
currently we’re hosting it on a VM with 32 GB of RAM (of which 30 are
dedicated to Solr and nothing else is running there). We have four
cores, that are this size:
- 25.56 GB, Num Docs = 57,860,845
- 12.09 GB
12 matches
Mail list logo
