Show problem with 'keys' command with specific command sequence.

[alicebob]

Hi Redis,

we encountered a small problem when the 'keys' command is misbehaving. Or at least not behaving as we expect. This test has the minimal sequence we need to reproduce.

Piping this to redis-cli gives similar results:

flushall
set a c
set t c
set e c
set s c
set foo b
expire s 5
keys *

[fgeller]

+1

[pietern]

Thanks for the report. For the completeness of the issue, for me the output of this snippet on 2.6-rc1 is:

$ cat | src/redis-cli
flushall
set a c
set t c
set e c
set s c
set foo b
expire s 5
keys *
OK
OK
OK
OK
OK
OK
(integer) 1
1) "e"
2) "a"
3) "s"

[pietern]

It appears to only manifest itself when EXPIRE gets called. When it is called before SET foo even weirder results for KEYS show up, including duplicates. I guess this is related to the incremental rehashing process.

[pietern]

Let's continue in #488.

@alicebob Thanks for reporting the issue and submitting a failing test.

[alicebob]

Excellent, thanks for the quick fix!

[antirez]

Thanks you for the report and the fix! Merging.