I believe that there used to be server IDs in here, but no longer. Peering in 1.5 seems to just ignore it, but 1.6 does something strange under load. Still haven't reproduced in a test environment, though.
On Wednesday, February 24, 2016, Bryan Talbot <bryan.tal...@ijji.com> wrote: > On Wed, Feb 24, 2016 at 6:05 PM, James Brown <jbr...@easypost.com > <javascript:_e(%7B%7D,'cvml','jbr...@easypost.com');>> wrote: > > > > We use a gpc0 counter for rate-limiting certain requests in our > application. It was working fine with 1.5.14, but as soon as I upgraded to > 1.6.3, we started seeing the gpc0_rate value go crazy – it's currently > showing values in the hundreds of thousands when the underlying gpc0 > counter has > > stick-table type string len 32 size 512 expire 5m store > gpc0,gpc0_rate(5m),http_req_rate(10s) peers lbsj > > > > > > > I didn't realize that stick tables without a server-id entry like this > would be replicated to remotes. My reading of the docs for 1.5 and 1.6 > stick-table peers option makes it seem like ONLY stick-table entries with a > server-id are replicated to remotes. Maybe this is not the case? > > Entries which associate keys to server IDs are kept synchronized with the > remote peers declared in this section. > > > > https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#stick-table > https://cbonte.github.io/haproxy-dconv/configuration-1.6.html#stick-table > > -Bryan > > > P.S. Now I think I know why we got a bunch of 'too many errors' responses > from EasyPost today! > > -- James Brown Engineer
