BrianChen
BrianChen
@rodolfobrunner Does this issue happen while using the same deployment as https://github.com/Kong/kong/issues/14144? I'm trying to reproduce it.
> request_latency_ms_bucket{service="customer-support",route="customer-support_getcards",workspace="default",le="00080.0"} null
@jmadureira For the `ngx.shared.DICT.incr(k,v)`, `v` will only take a number, so there should be no way `incr` write an `nil`, I started to doubt if there is issue in this...
@jmadureira Could you do more debug to clarify that: 1. are there warning logs to indicate write error when doing `self.dict:incr(k, v, 0)` operation. 2. could you use `ngx.shared.DICT.free_space` to...
> The error no longer shows up, most likely because since the value gets read immediately it won't be affected by the LRU logic. I think `incr` and `get` both...
> 2025/02/20 13:56:56 ... counter.lua:65: Synced 46 counters from worker nil: request_latency_ms_bucket{service="customer-support",route="customer-support_getcards",workspace="default",le="00080.0"}=old_value+1=1 current value=nil, ... Emm... That makes me feel suspicious about the `ngx.shared.DICT.incr` API. I think if that API...
That really confused me, As I saw from your debugging results: 1. `dict.incr` succeed and returns the value it stored, which is not `nil`. 2. `dict.get` returns `nil` even the...
@romanova09 I suggest you can upgrade kong to an new version (3.8.0 as the latest release) to check if this problem still exists. And for creating an issue, it's better...
@fffonion Could you help to check if this is by design, or an issue?