无效消息在同一连接中发送（仅在使用RESP3协议时可用）或在另一个不同的连接中（也可在RESP2和Pub / Sub中使用）。
CLIENT TRACKING on ... options ...
CLIENT TRACKING off 停止跟踪。
REDIRECT <id>: send redirection messages to the connection with the specified ID. The connection must exist, you can get the ID of such connection using CLIENT ID. If the connection we are redirecting to is terminated, when in RESP3 mode the connection with tracking enabled will receive
tracking-redir-brokenpush messages in order to signal the condition.
BCAST: enable tracking in broadcasting mode. In this mode invalidation messages are reported for all the prefixes specified, regardless of the keys requested by the connection. Instead when the broadcasting mode is not enabled, Redis will track which keys are fetched using read-only commands, and will report invalidation messages only for such keys.
PREFIX <prefix>: for broadcasting, register a given key prefix, so that notifications will be provided only for keys starting with this string. This option can be given multiple times to register multiple prefixes. If broadcasting is enabled without this option, Redis will send notifications for every key.
OPTIN: when broadcasting is NOT active, normally don't track keys in read only commands, unless they are called immediately after a
CLIENT CACHING yescommand.
OPTOUT: when broadcasting is NOT active, normally track keys in read only commands, unless they are called immediately after a
CLIENT CACHING nocommand.
NOLOOP: don't send notifications about keys modified by this connection itself.