On Mon, Nov 13, 2017 at 11:28 PM, James Stroehmann < james.stroehm...@proquest.com> wrote:
> I had a similar problem, and I believe reducing my ‘hold valid’ setting to > 1s fixed it. > > > > > Possible explanation is the "inter" parameter which is by default set to 2s for the "check" operation, see https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#inter for details. In other words, read the docs about ALL timeouts set in Haproxy to figure out how they correlate between each other and how to set the proper values for your user case. > *From:* DHAVAL JAISWAL [mailto:dhava...@gmail.com] > *Sent:* Monday, November 13, 2017 2:31 AM > *To:* HAproxy Mailing Lists <haproxy@formilux.org> > *Subject:* backend has no server available! > > > > [External Email] > > I had the following config where we are using AWS ELB for load balancing. > However, now we are keep getting backend test_cluster has no server > available! > > > > Under this ELB two servers attached. Both instance are in healthy state. > Healthy state we are checking on port 80 and tomcat response sending on > port 8080 > > > > internal-testtomcatautoscale-1314784611.ap-southeast-1.elb.amazonaws.com > > > > > > resolvers testresolver > > nameserver dns1 169.254.169.253:53 > > resolve_retries 3 > > timeout retry 1s > > hold valid 10s > > > > backend test_cluster > > mode http > > option forwardfor > > fullconn 10000 > > option httpchk /test-testalive > > http-check expect string OK > > option http-server-close > > option abortonclose > > balance roundrobin > > server server1 internal-testtomcatautoscale-1314784611.ap-southeast-1.elb. > amazonaws.com:8080 check resolvers testresolver > > > > > > What could be the cause of this issue. How can i fix it. > > > -- Igor Cicimov | DevOps p. +61 (0) 433 078 728 e. ig...@encompasscorporation.com <http://encompasscorporation.com/> w*.* www.encompasscorporation.com a. Level 4, 65 York Street, Sydney 2000
