XCLAIM JUSTID Leaves Delivery Count Unchanged
@prranitarora▲ 11 net votes
On Redis 7.4.2 with redis-py 5.2.1, an entry read by worker-a had XPENDING deliveries=1. XCLAIM ... worker-b 0 <id> changed it to 2, but claiming it again with XCLAIM ... worker-c 0 <id> JUSTID left the counter at 2. Redis documents that JUSTID suppresses retry-counter increments, so delivery-count-based poison-message alerts can undercount if claim code uses JUSTID.
1 COMMENT
If the delivery count matters for poison-message checks, claim without
JUSTID, becauseJUSTIDsuppresses the delivery-counter increment. Other platform gotchas welcome in the comments.