Re: Server weight in server-template and consul dns
On Mon, Apr 27, 2020 at 10:14 PM Baptiste wrote: > > > On Mon, Apr 27, 2020 at 3:05 AM Igor Cicimov < > ig...@encompasscorporation.com> wrote: > >> Hi, >> >> On Mon, Apr 20, 2020 at 10:25 PM Igor Cicimov < >> ig...@encompasscorporation.com> wrote: >> >>> Hi, >>> >>> I have the following template in a server backend: >>> >>> server-template tomcats 10 _tomcat._tcp.service.consul resolvers consul >>> resolve-prefer ipv4 check >>> >>> This is the SRV records resolution: >>> >>> # dig +short @127.0.0.1 -p 8600 _tomcat._tcp.service.consul SRV >>> 1 10 8080 ip-10-20-3-21.node.dc1.consul. >>> 1 10 8080 ip-10-20-4-244.node.dc1.consul. >>> >>> The server's weight reported by haproxy is 1 where I expected to see 10. >>> Just to clarify, is this expected or there is a mixup between priority and >>> weight? >>> >>> Thanks, >>> Igor >>> >>> >> Giving this another try. Maybe Baptiste can help to clarify which part of >> the SRV record is considered as server weight, the record priority or the >> record weight? >> >> Thanks, >> Igor >> >> >> > Hi, > > This is the record weight. > There is a trick for weights: DNS weight range if from 0 to 65535 while > HAProxy weight is from 0 to 256. So basically, your DNS weight is divided > by 256 before being applied. > so adjust your DNS weight accordingly. > > Baptiste > Thanks Baptiste, works as per your comment! Cheers, Igor
Re: Server weight in server-template and consul dns
On Mon, Apr 27, 2020 at 3:05 AM Igor Cicimov wrote: > Hi, > > On Mon, Apr 20, 2020 at 10:25 PM Igor Cicimov < > ig...@encompasscorporation.com> wrote: > >> Hi, >> >> I have the following template in a server backend: >> >> server-template tomcats 10 _tomcat._tcp.service.consul resolvers consul >> resolve-prefer ipv4 check >> >> This is the SRV records resolution: >> >> # dig +short @127.0.0.1 -p 8600 _tomcat._tcp.service.consul SRV >> 1 10 8080 ip-10-20-3-21.node.dc1.consul. >> 1 10 8080 ip-10-20-4-244.node.dc1.consul. >> >> The server's weight reported by haproxy is 1 where I expected to see 10. >> Just to clarify, is this expected or there is a mixup between priority and >> weight? >> >> Thanks, >> Igor >> >> > Giving this another try. Maybe Baptiste can help to clarify which part of > the SRV record is considered as server weight, the record priority or the > record weight? > > Thanks, > Igor > > > Hi, This is the record weight. There is a trick for weights: DNS weight range if from 0 to 65535 while HAProxy weight is from 0 to 256. So basically, your DNS weight is divided by 256 before being applied. so adjust your DNS weight accordingly. Baptiste
Re: Server weight in server-template and consul dns
Hi, On Mon, Apr 20, 2020 at 10:25 PM Igor Cicimov < ig...@encompasscorporation.com> wrote: > Hi, > > I have the following template in a server backend: > > server-template tomcats 10 _tomcat._tcp.service.consul resolvers consul > resolve-prefer ipv4 check > > This is the SRV records resolution: > > # dig +short @127.0.0.1 -p 8600 _tomcat._tcp.service.consul SRV > 1 10 8080 ip-10-20-3-21.node.dc1.consul. > 1 10 8080 ip-10-20-4-244.node.dc1.consul. > > The server's weight reported by haproxy is 1 where I expected to see 10. > Just to clarify, is this expected or there is a mixup between priority and > weight? > > Thanks, > Igor > > Giving this another try. Maybe Baptiste can help to clarify which part of the SRV record is considered as server weight, the record priority or the record weight? Thanks, Igor
Server weight in server-template and consul dns
Hi, I have the following template in a server backend: server-template tomcats 10 _tomcat._tcp.service.consul resolvers consul resolve-prefer ipv4 check This is the SRV records resolution: # dig +short @127.0.0.1 -p 8600 _tomcat._tcp.service.consul SRV 1 10 8080 ip-10-20-3-21.node.dc1.consul. 1 10 8080 ip-10-20-4-244.node.dc1.consul. The server's weight reported by haproxy is 1 where I expected to see 10. Just to clarify, is this expected or there is a mixup between priority and weight? Thanks, Igor
