We're seeing the same thing (though we're not using replication). Based on the trace, it looks like it would happen when Solr's response is too slow for the client, and it's trying to send a response back to someone who's no longer listening for one.

So, I think this isn't an error in itself so much as a side effect of a larger problem (like why the operation is taking so long).

--
Tom Lianza
CTO, Wishpot.com
skype: tlianza

Reply via email to