Re: gpc0_rate computing incorrectly with peer replication turned in [in 1.6.3]

Hi, On Wed, Feb 24, 2016 at 10:04:26PM -0800, James Brown wrote: > 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. Indeed, one of the

Re: gpc0_rate computing incorrectly with peer replication turned in [in 1.6.3]

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 wrote: > On Wed, Feb

Re: gpc0_rate computing incorrectly with peer replication turned in [in 1.6.3]

On Wed, Feb 24, 2016 at 6:05 PM, James Brown 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

gpc0_rate computing incorrectly with peer replication turned in [in 1.6.3]

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 *never*