The problem/use-case that the feature addresses When we want to get the last change of a cluster, we will use a mock slave get all command change
it works good in single redis node, but in cluster, beacuse slot may migrate between nodes, we will get a RESTORE command for a key in target and a DEL command for a key in source, out of cluster, we cannot figure out which is the REAL action, In fact, for us, NONE of them is available, because we dont care about slot migrate in cluster, we only want to know the data change by user
we need to firgure out this action
Description of the feature so if we can make a tag on command, or just use two different command, such as mrestore/mdel, in place of migrate/del in slot migrate, this will solve our problem
Alternatives you've considered any solution we can figure out slot migrate command is ok
Additional information we have same problem in mongodb, and mongodb has a "fromMigrate": true tag in oplog document, so we can ignore it safety
In a cluster system, we think maybe its necessary to get what action is by user, what actiob is not, beacuse data is like a stream, it goes from different system, and go to different system, like water
all action is system itself should be hidden to user, only action by user can be shown
thanks for reading, wish to reply
Comment From: enjoy-binbin
looks interesting / reasonable, please share your thought @madolson @zuiderkwast
Comment From: judeng
I allso have the same problem，it souds good to add a comment command such as migrating, just like caching 、asking command, and persistence the tag in aof file