CLUSTERGETKEYSINSLOT continues to return the same keys even after they've been migrated

[priyanjgupta]

Describe the bug

CLUSTERGETKEYSINSLOT returns an array of keys stored in the contacted node which are mapped to the specified hash slot. But when the node is in MIGRATING state, if some keys have migrated and the CLUSTERGETKEYSINSLOT function is called again, it returns the same keys, including those that have been migrated.

Steps to reproduce the bug

Repro:

1. Create a cluster comprising of two nodes, N1 and N2.
2. Add some slots to N1
3. Add keys mapped to a slot X served by N1
4. Set the target node N2 in importing state to import slot X from node N1
5. Set the source node N1 in migrating state to migrate slot X to node N2
6. Call ClusterGetKeysInSlot for slot X on N1
7. Migrate an existing key, K1, mapped to slot X from N1 to N2
8. Call ClusterGetKeysInSlot for slot X on N1
9. K1, along with any other existing keys, will be included in the returned result.

Expected behavior

Following the migration of key K1 from the source node, when invoking ClusterGetKeysInSlot, the returned result should not include the migrated key K1.

Screenshots

Release version

No response

IDE

No response

OS version

No response

Additional context

No response