CLIENT KILL关闭一个指定的连接。在Redis2.8.11时可以根据客户端地址关闭指定连接,关闭方式如下:

CLIENT KILL addr:port

ip:port应该是CLIENT LIST 命令里面列出的客户端连接之一。

然而,从Redis 2.8.12开始,这个命令改为如下格式:

CLIENT KILL <filter> <value> ... ... <filter> <value>

新的格式可以根据不同属性杀死客户端而不是只按地址杀死。他们有以下一些格式:

  • CLIENT KILL ADDR ip:port. 和旧版的三个参数时的行为完全一样。
  • CLIENT KILL ID client-id. 可以通过唯一ID字段杀死一个客户端,唯一ID可以通过Redis2.8.12的CLIENT LIST命令查询。
  • CLIENT KILL TYPE type, 这里的 type 可以是 normal, slave, pubsub。 这将关闭所有特殊类的客户端. 请注意被认为是属于正常类的客户端将会被MONITOR命令监视到。
  • 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 no will 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: 可以在执行命令时同时给定多个筛选条件。该命令会使用逻辑AND来处理多个筛选条件,比如:

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. 是可以的,并且只会杀死给定IP地址的的slave。这种包含多个筛选条件的格式目前很少使用。

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. 当使用新的格式时,该命令不再返回OK或者错误,而是返回被杀死的客户端个数,有可能为0.

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. 当前版本的Redis Sentinel 可以在实例被重新配置的时候使用CLIENT KILL 杀死客户端。这样可以强制客户端和一个Sentinel重新连接并更新自己的配置。

Notes

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). 因为Redis的单线程属性,不可能在客户端执行命令时杀掉它. 从客户端的角度看,永远无法杀死一个正在执行命令的连接。 但是当客户端发送下一条命令时会意识到连接已被关闭,原因为网络错误。

@return

When called with the three arguments format: 三参数格式执行命令: @simple-string-reply: OK if the connection exists and has been closed @simple-string-reply: 连接存在并被关闭返回OK

When called with the filter / value format: 过滤/值格式执行命令: @integer-reply: the number of clients killed. @integer-reply: 被杀死的客户端个数