Unfortunately, doesn't look like this clears the symptom.
The ping is responding almost instantly every time. I've tried setting a 15 second timeout on the check, with no change in occurences of the error.
Looking at a packet capture on the server side, there is a clear distinction between working and failing/error-triggering connections.
It looks like in a "working" case, I see two packets immediately back to back (one with header, and next a continuation with content) with no ack in between, followed by ack, rst+ack, rst.
In the failing request, I see the GET request, acked, then the http/1.1 200 Ok response from Solr, a single ack, and then an almost instantaneous reset sent by the client.
I'm only seeing this on traffic to/from haproxy checks. If I do a simple:
while [ true ]; do curl -s http://host:8983/solr/admin/ping; done
from the same box, that flood runs with generally 10-20ms request times and
zero errors.
-- Nathan
On 07/27/2014 07:12 PM, Nathan Neulinger wrote:
Cool. That's likely exactly it, since I don't have one set, it's using the check interval, and occasionally must just be too short. Thank you! -- NathanI assume that this is the httpchk config to make sure that the server is operational. If so, you need to increase the "timeout check" value, because it is too small. The ping request is taking longer to run than you have allowed in the timeout. Here's part of my haproxy config:
-- ------------------------------------------------------------ Nathan Neulinger nn...@neulinger.org Neulinger Consulting (573) 612-1412
solr-working.cap
Description: application/vnd.tcpdump.pcap
solr-cutoff2.cap
Description: application/vnd.tcpdump.pcap
