For people who have same issue, solved solved adding:
text
in the requestHandler /update/extract" in solrconfig.xml:
last_modified
ignored_
* text*
-MM-dd
So no need to add content in solrj:
p.setParam("literal.text",handler.toString());
R
After some more debugging I have found out, that one of the requests had a
size of 4,4MB. The default maxPostSize in tomcat6 is 2MB (
http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html).
Changing that to 10MB has greatly improved situation on the solr side.
Dmitry
On Fri, May 3, 2013 at 9:
Digging in further, found this in HttpCommComponent class:
[code]
static {
MultiThreadedHttpConnectionManager mgr = new
MultiThreadedHttpConnectionManager();
mgr.getParams().setDefaultMaxConnectionsPerHost(20);
mgr.getParams().setMaxTotalConnections(1);
mgr.getParams().setCon
Hi, thanks.
Solr 3.4.
There is POST request everywhere, between client and router, router and
shards.
Do you do faceting across all shards? How many documents approx you have?
On 2 May 2013 22:02, "Patanachai Tangchaisin" <
patanachai.tangchai...@wizecommerce.com> wrote:
> Hi,
>
> First, which v
Hi,
First, which version of Solr are you using?
I also has 60 shards+ on Solr 4.2.1 and it doesn't seems to be a problem
for me.
- Make sure you use POST to send a query to Solr.
- 'connection reset by peer' from client can indicate that there is
something wrong with server e.g. server closes a
After some searching around, I see this:
http://search-lucene.com/m/ErEZUl7P5f2/%2522socket+write+error%2522&subj=Long+list+of+shards+breaks+solrj+query
Seems like this has happened in the past with large amount of shards.
To make it clear: the distributed search works with 20 shards.
On Thu,
