ptimize would you recommend? We're
>> on 3.6.1 btw...
>>
>> Thanks,
>> Robi
>>
>> -Original Message-
>> From: Erick Erickson [mailto:erickerick...@gmail.com]
>> Sent: Thursday, October 11, 2012 5:29 AM
>> To: solr-user@lucene.apach
s,
> Robi
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Thursday, October 11, 2012 5:29 AM
> To: solr-user@lucene.apache.org
> Subject: Re: anyone have any clues about this exception
>
> Well, you'll actually be ab
org
Subject: Re: anyone have any clues about this exception
Well, you'll actually be able to optimize, it's just called forceMerge.
But the point is that optimize seems like something that _of course_ you want
to do, when in reality it's not something you usually should do at all
iginal Message-
> From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> Sent: Wednesday, October 10, 2012 11:10 AM
> To: solr-user@lucene.apache.org
> Subject: Re: anyone have any clues about this exception
>
> Something timed out, the other end closed the connection. This end trie
0, 2012 11:10 AM
To: solr-user@lucene.apache.org
Subject: Re: anyone have any clues about this exception
Something timed out, the other end closed the connection. This end tried to
write to closed pipe and died, something tried to catch that exception and
write its own and died even worse? Just ma
Something timed out, the other end closed the connection. This end
tried to write to closed pipe and died, something tried to catch that
exception and write its own and died even worse? Just making it up
really, but sounds good (plus a 3-year Java tech-support hunch).
If it happens often enough, s
Tomcat localhost log (not the catalina log) for my solr 3.6.1 (master)
instance contains lots of these exceptions but solr itself seems to be doing
fine... any ideas? I'm not seeing these exceptions being logged on my slave
servers btw, just the master where we do our indexing only.
Oct 9,
