Steps to repro:

  1. Set-up three instances (in three separate terminals or whatever) of redis-server:
$ redis-server --port 30001 --cluster-enabled yes --cluster-config-file nodes-30001.conf --cluster-node-timeout 100 --appendonly no --save "" --requirepass qwerty
$ redis-server --port 30002 --cluster-enabled yes --cluster-config-file nodes-30002.conf --cluster-node-timeout 100 --appendonly no --save "" --requirepass qwerty
$ redis-server --port 30003 --cluster-enabled yes --cluster-config-file nodes-30003.conf --cluster-node-timeout 100 --appendonly no --save "" --requirepass qwerty
  1. Configure cluster via redis-cli:
$ src/redis-cli --cluster create 127.0.0.1:30001 127.0.0.1:30002 127.0.0.1:30003 --cluster-replicas 0 -a qwerty

I'm using the most recent redis-cli and redis-benchmark from unstable-branch.

  1. Verify, that cluster is "ok":
$ src/redis-cli -h 127.0.0.1 -p 30001 -a qwerty -c cluster info
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:3
cluster_size:3
cluster_current_epoch:3
cluster_my_epoch:1
cluster_stats_messages_sent:2092
cluster_stats_messages_received:2092
  1. Try to benchmark against assembled cluster:
$ src/redis-benchmark -h 127.0.0.1 -p 30001 -a qwerty -c 100 -n 100 -t set --cluster
Cluster node 127.0.0.1:30001 replied with error:
NOAUTH Authentication required.
Failed to fetch cluster configuration from 127.0.0.1:30001

If I turn off redis authentication, benchmark works like charm.

Comment From: artix75

@VassyutovichIlya Which version are you using?

Comment From: IlyaVassyutovich

@artix75 I'm using redis-server 5.0.5 and redis-cli and redis-benchmark from unstable-branch. Just checked — can reproduce at antirez/redis@2400f5782e2b22ee0131b6a8eeb8d7a4abb22088.

Comment From: filipecosta90

@IlyaVassyutovich closing this one given it was fixed by #7488