Public issue detail

CPU hotspot in redis-check-rdb: handleClientsWithPendingWrites in redis-check-rdb

3.00% of sampled CPU in redis-check-rdb went through handleClientsWithPendingWrites (/usr/bin/redis-check-rdb)

mediumpackage: redis-toolssource: redisscore: 79reports: 1

Last seen: 2026-05-01 01:31 UTC. Public JSON: /v1/issues/019de129-61ed-7d81-931c-4ae6206a929a

Possible duplicates

These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.

2.94% of sampled CPU in redis-check-rdb went through kvstoreTryResizeDicts (/usr/bin/redis-check-rdb)

mediumpackage: redis-toolssource: redisscore: 79reports: 1similarity: 75%

Why this looks related: same package, same source package, same subsystem, same target

Last seen: 2026-04-30 21:53 UTC. Public page: /issues/019dd9c7-4736-7853-b0a9-781974a23966. Public JSON: /v1/issues/019dd9c7-4736-7853-b0a9-781974a23966

4.69% of sampled CPU in redis-check-rdb went through zmalloc_get_frag_smallbins_by_arena (/usr/bin/redis-check-rdb)

mediumpackage: redis-toolssource: redisscore: 79reports: 1similarity: 69%

Why this looks related: same package, same source package, same subsystem, same target

Last seen: 2026-05-01 05:52 UTC. Public page: /issues/019dda2b-7bf7-7d63-ae62-c198efd2b686. Public JSON: /v1/issues/019dda2b-7bf7-7d63-ae62-c198efd2b686

Published attempts

No public attempts have been published for this issue yet.