Hi,

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?


cheers


On Thu, Jan 3, 2013 at 4:56 AM, Shawn Heisey <[email protected]> wrote:
> I am running haproxy as a front end for Solr and Mule, currently on 1.5dev7.
> There are some occasional weird moments where haproxy marks the primary solr
> server as offline and sends requests to the next server.  At this time I
> have no reason to think Solr is actually having a problem, so I want to try
> a newer 1.5dev release.  I saw that 1.5dev15 and 1.5dev16 had some critical
> issues.  Is anyone aware of any issues in 1.5dev17 that might affect the
> following simple config?  I'm on CentOS 6.3, kernel is
> 2.6.32-279.19.1.el6.centos.plus.x86_64.
>
> global
>         log 127.0.0.1   local0
>         log 127.0.0.1   local1 notice
>         #log loghost    local0 info
>         maxconn 4096
>         daemon
>         #debug
>         #quiet
>         spread-checks   2
>
> defaults
>         log     global
>         mode    http
>         option  httplog
>         option  dontlognull
>         option  redispatch
>         option  abortonclose
> #       option  httpclose
>         option  http-server-close
>         option  http-pretend-keepalive
>         retries 1
>         maxconn 1024
>         timeout connect 1000
>         timeout client  1000
>         timeout server  30000
>         timeout check   5000
>
> listen  stats 0.0.0.0:8080
>         stats uri /
>
> listen  idx
>         bind 0.0.0.0:8983
>         bind 0.0.0.0:8984
>         option  httpchk GET /solr/ncmain/admin/ping
>         balance roundrobin
>         server  idxa1 10.100.0.240:8981 check inter 5000 fastinter 2000 rise
> 2 fall 1 weight 100
>         server  idxb1 10.100.0.241:8981 check inter 5000 fastinter 2000 rise
> 2 fall 1 weight 100 backup
>         server  idxa2 10.100.0.242:8981 check inter 60000 fastinter 2000
> rise 2 fall 1 weight 2 backup
>         server  idxb2 10.100.0.243:8981 check inter 60000 fastinter 2000
> rise 2 fall 1 weight 1 backup
>
> listen  mule
>         bind 0.0.0.0:8777
>         no option       http-server-close
>         no option       http-pretend-keepalive
>         option  httpchk GET /services/ApsService/testAlive
>         balance roundrobin
>         server  frontier 10.100.0.25:8777 check inter 5000 fastinter 2000
> rise 2 fall 1 weight 100
>         server  fremont 10.100.0.26:8777 check inter 5000 fastinter 2000
> rise 2 fall 1 weight 100
>         server  fiesta 10.100.0.29:8777 check inter 5000 fastinter 2000 rise
> 2 fall 1 weight 100 backup
>

Reply via email to