This is a pretty minor issue, but you might want to know. I'm running the following command:
./redis-benchmark -t PING_MBULK -p 5555 -c 10 -P 5
And it results in many such messages when running redis with verbose loglevel.
Reading from client: Connection reset by peer
I first noticed this when benchmarking my own redis-like server, and the same error appeared there. So I believe this is an issue in redis-benchmark, not the servers, and the messages only appear when pipelining is set to anything larger than 1.
Version:
Redis server v=3.2.0 sha=00000000:0 malloc=jemalloc-4.0.3 bits=64 build=c626b9bdd9962da6
Comment From: huangzhw
Never see it.
Comment From: oranagra
just closing the connection is a valid way to shut it down, no need for anything else. if you enable verbose or debug logging you'll see a lot logs, might not suitable for benchmark.