Re: Solr Suggest Component and OOM

2018-07-01 Thread Ratnadeep Rakshit
Has anyone ever been successful in processing 150M records using the Suggester Component? The make of the component, please comment. On Tue, Jun 26, 2018 at 1:37 AM, Ratnadeep Rakshit wrote: > The site_address field has all the address of United states. Idea is to > build something similar to Go

Re: Solr Suggest Component and OOM

2018-06-25 Thread Ratnadeep Rakshit
The site_address field has all the address of United states. Idea is to build something similar to Google Places autosuggest. Here's an example query: curl " http://localhost/solr/addressbook/suggest?suggest.q=1054%20club&wt=json"; Response: { "responseHeader": { "status": 0, "QTime": 3125, "par

Re: Solr Suggest Component and OOM

2018-06-14 Thread Alessandro Benedetti
I didn't get any answer to my questions ( unless you meant you have 25 millions of different values for those fields ...) Please read again my answer and elaborate further. Do you problem happen for the 2 different suggesters ? Cheers - --- Alessandro Benedetti Search Consultant

Re: Solr Suggest Component and OOM

2018-06-14 Thread Ratnadeep Rakshit
Anyone from the Solr team who can shed some more light? On Tue, Jun 12, 2018 at 8:13 PM, Ratnadeep Rakshit wrote: > I observed that the build works if the data size is below 25M. The moment > the records go beyond that, this OOM error shows up. Solar itself shows 56% > usage of 20GB space during

Re: Solr Suggest Component and OOM

2018-06-12 Thread Ratnadeep Rakshit
I observed that the build works if the data size is below 25M. The moment the records go beyond that, this OOM error shows up. Solar itself shows 56% usage of 20GB space during the build. So, is there some settings I need to change to handle larger data size? On Tue, Jun 12, 2018 at 3:17 PM, Aless

Re: Solr Suggest Component and OOM

2018-06-12 Thread Alessandro Benedetti
Hi, first of all the two different suggesters you are using are based on different data structures ( with different memory utilisation) : - FuzzyLookupFactory -> FST ( in memory and stored binary on disk) - AnalyzingInfixLookupFactory -> Auxiliary Lucene Index Both the data structures should be v

Re: Solr Suggest Component and OOM

2018-06-11 Thread Ratnadeep Rakshit
Can anyone put some light on this? On Tue, Jun 12, 2018 at 12:32 AM, Ratnadeep Rakshit wrote: > Here's the stack trace : > > 538 ERROR - 2018-06-07 09:07:36.030; [ x:addressbook] > org.apache.solr.common.SolrException; null:java.lang.RuntimeException: > java.lang.OutOfMemory > > Error: Java h

Re: Solr Suggest Component and OOM

2018-06-11 Thread Ratnadeep Rakshit
Here's the stack trace : 538 ERROR - 2018-06-07 09:07:36.030; [ x:addressbook] org.apache.solr.common.SolrException; null:java.lang.RuntimeException: java.lang.OutOfMemory Error: Java heap space 539 at org.apache.solr.servlet.HttpSolrCall.sendError(HttpSolrCall.java:607) 540

Re: Solr Suggest Component and OOM

2018-06-11 Thread Christopher Schultz
Ratnadeep, On 6/11/18 12:25 PM, Ratnadeep Rakshit wrote: > I am using the Solr Suggester component in Solr 5.5 with a lot of address > data. My Machine has allotted 20Gb RAM for solr and the machine has 32GB > RAM in total. > > I have an address book core with the following vitals - > > "numDocs

Solr Suggest Component and OOM

2018-06-11 Thread Ratnadeep Rakshit
I am using the Solr Suggester component in Solr 5.5 with a lot of address data. My Machine has allotted 20Gb RAM for solr and the machine has 32GB RAM in total. I have an address book core with the following vitals - "numDocs"=153242074 "segmentCount"=34 "size"=30.29 GB My solrconfig.xml looks s