From 434e97a4b8c481bfc5d04dbc158a74cd8cc7aeb1 Mon Sep 17 00:00:00 2001 From: Vladimir Dementyev Date: Mon, 18 Mar 2024 15:58:44 -0700 Subject: [PATCH] trouble: redis cache --- docs/troubleshooting.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 36b9cf0..8f95071 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -1,5 +1,9 @@ # Troubleshooting 🔥 +## `Failed to connect to Redis: unknown command 'CLIENT', with args beginning with: 'TRACKING'` + +Some managed Redis (e.g., Google Cloud) providers block many Redis commands, including [client-side server tracking](https://redis.io/commands/client-tracking/), which is enabled in AnyCable by default. If you experience this issue, set the `--redis_disable_cache` flag (or `ANYCABLE_REDIS_DISABLE_CACHE=true`). + ## `ActionCable.server.broadcast` doesn't send messages The most common problem is using different Redis channels within RPC instance and `anycable-go`. Find the following line in the logs: