You only have 261 documents. That shouldn't be a problem, unless your document
size is huge.
I feel, the problem still exists somewhere. You have just deferred it...
Bosco
On Tue, Dec 8, 2015 at 6:48 AM -0800, "Salman Ansari"
wrote:
Thanks Andrea and Alexandre for your responses.
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.
Re
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 an
I would set up logging in the admin console (queries should be logged out
by default), and then check the difference between the two invocations.
I don't believe the two clients are doing the *same* thing, there should be
some difference.
Another chance could be that the OOM is just behind the cor
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?
