1) redis server 6.0.3 started with command CONFIG renamed 2) $ redis-benchmark ERROR: ERR unknown command CONFIG, with args beginning with: GET, save, ERROR: failed to fetch CONFIG from 127.0.0.1:6379

the reason is those 2 lines: redisAppendCommand(c, "CONFIG GET %s", "save"); redisAppendCommand(c, "CONFIG GET %s", "appendonly");

Comment From: ShooterIT

Yes, Benchmark couldn't get configurations if 'CONFIG' is renamed. But I think it doesn't matter. We do pressure tests in development stage and there is no need to rename config command.

Comment From: oranagra

@ShooterIT @huangzhw I think this this is (was) a valid bug report. CONFIG is a sensitive command and many people want to disable it in production deployments, either by rename-command or ACL. On the other hand, people wanna benchmark their production setups, for various reasons (even if to tweak other configurations).

however this 6.0 bug was already fixed. here's 6.2:

$ src/redis-server --rename-command config bla &
...
127.0.0.1:6379> config set save ""
(error) ERR unknown command `config`, with args beginning with: `set`, `save`, ``, 
...
$ src/redis-benchmark 
ERROR: ERR unknown command `CONFIG`, with args beginning with: `GET`, `save`, 
ERROR: failed to fetch CONFIG from 127.0.0.1:6379
WARN: could not fetch server CONFIG
====== PING_INLINE ======                                                     
...