On Tue, Apr 24, 2018 at 05:22:39PM +0200, Willy Tarreau wrote: > Slawa, > > I have a question below : > > backend default-pool > balance roundrobin > option httpchk GET /health-check > timeout connect 1000ms > timeout server 5000ms > server elb1 x.eu-west-1.elb.amazonaws.com:80 maxconn 7000 id 1 > check resolvers mydns resolve-prefer ipv4 > server elb2 y.eu-west-1.elb.amazonaws.com:80 maxconn 7000 id 2 > check resolvers mydns resolve-prefer ipv4 > (...) > resolvers mydns > nameserver dns1 8.8.8.8:53 > resolve_retries 3 > timeout retry 1s > hold other 30s > hold refused 30s > hold nx 30s > hold timeout 30s > hold valid 10s > > Do you think the issue described below could have any effect on your use > case, such as forcing frequent changes, updates or up/down ? Just trying > to narrow down the possible trigger for the problem (I still failed to > see it for now, even after sending lots of HTTP traffic and DNS responses) :
My issuse don't originate in ordinary run time: if issuse don't exist now -- issuse don't exist in future until reload. I am don't see issuse after start. I am see this issuse after reload, imeediatly after reload. Not every reload caused this. > https://www.reddit.com/r/sysadmin/comments/8ejrkk/google_dns_issues/ I mean not related to me. PS: I am try to distribute frontend to cores and failed: global nbproc 1 nbthread 16 cpu-map auto:1/1-16 0-15 listen stats bind :9999 frontend balancer bind x.x.x.221:80 bind x.x.x.221:443 ssl crt xxxx bind-process 1/1-1/8 frontend tcp1 bind x.x.x.206:443 bind-process 1/9-1/16 mode tcp frontend tcp2 bind x.x.x.207:443 bind-process 1/9-1/16 mode tcp frontend tcp3 bind x.x.x.208:443 bind-process 1/9-1/16 mode tcp No addtional configuration in backends sections and I am not show backend configuration. TCP load rise CPU use on all core (0-15), I am expect rise CPU use only on 8-15 core. What I am miss?
