1. set "appendonly yes"
  2. invokes RedisModule_Replicate function with format "v!A" which is expected nothing to be written to aof file. RedisModule_Replicate(ctx, RedisModule_StringPtrLen(argv[0], NULL), "v!A", cmdargv, cmdargc);
  3. actually something is written as below. 1 $5 MULTI 1 $4 EXEC

Can it be fixed or improved? I don't expect write anything in this situation. then that would be cool we can realize to select storing data to memory(e.g.to implement new native data types) or to file in same redis instance.

Comment From: antirez

Yep the implementation is currently not correct if I remember correctly. Putting this in the Redis 6 GA milestone.

Comment From: antirez

@zh1029 sorry but handling this for Redis 6 is complex. The problem is that, when we emit MULTI we still don't really know if the next RM_Replicate() commands will emit just in the AOF or replication stream. We may modify Redis in the future releases, to postpone emitting MULTI in the future, but this poses certain problems as well. There is to design a better solution to improve this, but right now is hard in this cycle fo the release. Leaving it open but removing from the Redis 6 target.