Hi Maciej! On Fri, Oct 24, 2025 at 09:22:38PM +0200, Maciej Zdeb wrote: > Hi, > we noticed this, however the effect was not that dramatic, because of the > canary deployment of new haproxy versions. That canary just filled the > caches and after a couple of days the hit-ratio just got back to normal and > we could continue with haproxy upgrade. Actually we didn't investigate this > as a bug, but just assumed something changed in haproxy internals that > slightly affected the hashing. ;)
OK, good to know! > I still vote for fixing and backporting. In our case we will just notice > again a hit-ratio decrease during the next haproxy upgrade. Thanks for the feedback, it was backported to 3.2 already (3.2.7). Others will follow soon (maybe next week or the week after). > I presume other > users that have "huge/fragile" caching layers are always doing some kind of > canary deployment of new haproxy versions. Clearly, given that the only report I god was someone failing to migrate to 3.0+ because of it, I think that in most situations the margin is sufficient to absorb the shock. thanks! willy
