Just to clarify, the error is being thrown FROM a search, DURING an update.
This error is making distributed SOLR close to unusable for me. Any ideas?
Does SOLR fail on searches if one node takes too long to respond?
hossman wrote:
>
> : Hi,
> : I'm running a distributed solr index (3 nod
: Hi,
: I'm running a distributed solr index (3 nodes) and have noticed frequent
: exceptions thrown during updates. The exception (see below for full trace)
what do you mean "during updates" ? ... QueryComponent isn't used at all
when updating hte index, so there may be a missunderstanding here
I'm using a very slightly modified version of a nightly build from the middle
of September.
It seems like this isn't the only report of problems of this sort:
http://markmail.org/message/zept5u3hv4ytunfv#query:solr%20commit%20connection%20reset%20mergeids+page:1+mid:aqzaaphbuow4sa5o+state:resu
What version are you using? If a nightly build, from when?
Thanks
Erick
On Wed, Dec 2, 2009 at 12:53 PM, smock wrote:
>
> Hi,
> I'm running a distributed solr index (3 nodes) and have noticed frequent
> exceptions thrown during updates. The exception (see below for full trace)
> occurs in the
