On 1/2/2013 11:15 PM, Baptiste wrote:
dev17 fixes bugs from dev16 with no know regression or bugs for now...
Concerning your error, you consider one check failing to concider your
server as unoperational...
Try increasing this number to 2, to avoid "false positive".
Is it possible you reach a connection limit on your apache server and
your health check fails because of that?
I don't think it's a connnection limit (Jetty maxThreads of 10000, load
is NOT that high). I did however manage to correlate some exceptions in
the Jetty log with some of the DOWN notifications, so I think haproxy is
doing OK here. I'll follow up on the solr mailing list.
I may upgrade haproxy anyway, after waiting a while to see if any
regressions surface.
Thanks,
Shawn
