Thanks Andrea and Alexandre for your responses. Indeed it was the problem that Solr.NET was returning many rows (as I captured this by fiddler). Currently, my setup has only 500MB of JVM (which I will definitely increase) but at least I found the culprit by reducing the number of rows returned.
Regards, Salman On Tue, Dec 8, 2015 at 5:30 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > Solr by default only returns 10 rows. SolrNet by default returns many > rows. I don't know why that would cause OOM, but that's definitely > your difference unless you dealt with it: > > https://github.com/mausch/SolrNet/blob/master/Documentation/Querying.md#pagination > > Regards, > Alex. > ---- > Newsletter and resources for Solr beginners and intermediates: > http://www.solr-start.com/ > > > On 8 December 2015 at 07:52, Salman Ansari <salman.rah...@gmail.com> > wrote: > > Hi, > > > > I have created a cluster of Solr and Zookeepers on 3 machines connected > > together. Currently, I am facing a weird problem. My collection has only > > 261 documents and when I try to query the documents using the browser > such > > as > > > > http:// > > [ASolrServerInTheCluster]:8983/solr/sabrLocationsStore/select?q=(*:*) > > > > it returns the documents properly. However, when I try to do the same > using > > Solr.NET, it throws java.lang.OutOfMemoryError: Java heap space exception > > (although I have very few documents there). Any ideas why I am getting > this > > error? > > > > Regards, > > Salman >
