Repository navigation
A stream's DEBUG DIGEST-VALUE changes after AOF replay: consumer times are taken from the replay #505
Description
After an AOF replay, a stream's DEBUG DIGEST-VALUE differs from before the restart, even with plain text group and consumer names. That's because consumers' seen/active times are set from the replay rather than kept. Anything that compares digests across a restart, or between a master and a replica fed from AOF, sees a difference with no data having changed.
Expected: decide whether consumer times belong in the digest (Redis's DEBUG DIGEST-VALUE covers the stream's contents). Then either exclude them, or carry them through the AOF so the digest stays stable.
Found while testing binary keys PR 3 (#504), whose round-trip test works around it.
Activity