Open uvletter opened 1 year ago
I debug redis-6.2.6 and it work correctly, may have some state not cleaned up, you can try reboot redis or OS, and retry it.
If the issue still exists, you can gdb redis and show me the full stack trace.
Thx, it's not a stable issues, the busy loop seems to happen in refcount_acquire_if_gt
. If I re-compile the whole fstack as well as freebsd, the problem seems to disappear, but sometimes after a compilation it appears again. I didn't dive into this problem, keep it here for a record.
I keep getting this often at higher rates, sometime comes too many times and sometimes doesnt come. same backtrace while setting NONBLOCK for socket options did you find any solution to this? @uvletter @jfb8856606
Nope, I have no idea about how it occurs. I find trigger a freebsd recompilation by mutating the redcount.h
can forbid it.
My redis program is blocking at the startup, and the CPU runs to 100%, it seems like a busy loop.
When I gstack the process the stacktrace looks like