On 8/16/2016 8:53 PM, Jaspal Sawhney wrote:
> We are running solr 4.6 in master-slave configuration where in our master is
> used entirely for indexing. No search traffic comes to master ever.
> Off late we have started to get the early EOF error on the solr Master which
> results in a Broken
>From my testing program, there's nothing standard here.
As the blog points out, since I was indexing fairly
simple documents you should _not_ be expecting to
see those indexing rates. The point of the article was
just to show the _relative_ changes when I sent
batches.
Best,
Erick
On Wed, Aug
Erick
Going through the article which you shared. Where are you getting the
Docs/second value?
Thanks
On 8/17/16, 4:37 PM, "Jaspal Sawhney" wrote:
>Erick
>Thanks - My batch size was 30 and thread size also 30.
>Thanks
>
>On 8/17/16, 3:48 PM, "Erick Erickson"
Erick
Thanks - My batch size was 30 and thread size also 30.
Thanks
On 8/17/16, 3:48 PM, "Erick Erickson" wrote:
>What this probably indicates is that the size of the packets you send
>to Solr is large enough that it exceeds the transport protocol's
>limit. This is
What this probably indicates is that the size of the packets you send
to Solr is large enough that it exceeds the transport protocol's
limit. This is reinforced by your statement that reducing the batch
size fixes the problem even though it increases indexing time.
So the place I'd be looking is
Bump !
On 8/16/16, 10:53 PM, "Jaspal Sawhney" wrote:
>Hello
>We are running solr 4.6 in master-slave configuration where in our master
>is used entirely for indexing. No search traffic comes to master ever.
>Off late we have started to get the early EOF error on the solr
Hello
We are running solr 4.6 in master-slave configuration where in our master is
used entirely for indexing. No search traffic comes to master ever.
Off late we have started to get the early EOF error on the solr Master which
results in a Broken Pipe error on the commerce application from