CLIENT KILL addr:port
CLIENT LIST 命令里面列出的客户端连接之一。
CLIENT KILL <filter> <value> ... ... <filter> <value>
CLIENT KILL ADDR ip:port. 和旧版的三个参数时的行为完全一样。
CLIENT KILL ID client-id. 可以通过唯一
CLIENT KILL TYPE type, 这里的 type 可以是
pubsub。 这将关闭所有特殊类的客户端. 请注意被认为是属于正常类的客户端将会被
CLIENT KILL SKIPME yes/no. By default this option is set to
yes, that is, the client calling the command will not get killed, however setting this option to
nowill have the effect of also killing the client calling the command.
It is possible to provide multiple filters at the same time. The command will handle multiple filters via logical AND. For example:
CLIENT KILL addr 127.0.0.1:6379 type slave
is valid and will kill only a slaves with the specified address. This format containing multiple filters is rarely useful currently.
When the new form is used the command no longer returns
OK or an error, but instead the number of killed clients, that may be zero.
CLIENT KILL and Redis Sentinel
Recent versions of Redis Sentinel (Redis 2.8.12 or greater) use CLIENT KILL in order to kill clients when an instance is reconfigured, in order to force clients to perform the handshake with one Sentinel again and update its configuration.
Due to the single-threaded nature of Redis, it is not possible to kill a client connection while it is executing a command. From the client point of view, the connection can never be closed in the middle of the execution of a command. However, the client will notice the connection has been closed only when the next command is sent (and results in network error).
When called with the three arguments format:
OK if the connection exists and has been closed
When called with the filter / value format:
@integer-reply: the number of clients killed.