🔥 ccloud/fm-redis-sink #7427
Description
🆕💥 New issue !
🔥 CP 8.1.1 🕐 2025-12-04 10:38 📄 fully-managed-redis-sink.sh 🔗 https://github.com/vdesabou/kafka-docker-playground/actions/runs/19921980533/job/57113131361
Logs
10:24:15 ℹ️ 💀 kill all docker containers (disable with 'playground config container-kill-all-before-run false')
10:24:15 ℹ️ 💀 kill all docker containers
10:24:16 ℹ️ 🚀⛅ Running ccloud example with flags
10:24:16 ℹ️ ⛳ Flags used are --tag=8.1.1
10:24:17 ℹ️ 🚀 Number of examples ran so far: 4
10:24:17 ℹ️ 🤖CI status: 🟢 ok
🔗test url: https://github.com/vdesabou/kafka-docker-playground/actions/runs/19802914128/job/56733006820
10:24:17 ℹ️ ####################################################
10:24:17 ℹ️ 🚀 Executing fully-managed-redis-sink.sh in dir /home/runner/work/kafka-docker-playground/kafka-docker-playground/ccloud/fm-redis-sink
10:24:17 ℹ️ ####################################################
10:24:17 ℹ️ 🧰 Checking if Docker image confluentinc/cp-server-connect-base:8.1.1 contains additional tools
10:24:17 ℹ️ ⏳ it can take a while if image is downloaded for the first time
10:24:18 ℹ️ 🛰️ Starting up Confluent Platform in Kraft mode as ENABLE_KRAFT environment variable is set
10:24:18 ℹ️ ⛺ log in to Confluent Cloud
Logged in as "[email protected]" for organization "c66693c0-bd8e-408c-a551-95e6f766b29b" ("Confluent").
10:24:21 ℹ️ 🌱 CLUSTER_NAME is set, your existing Confluent Cloud cluster will be used...
10:24:21 ℹ️ 🌐 ENVIRONMENT is set with env-519yzz
10:24:21 ℹ️ 🎰 CLUSTER_NAME is set with aws
10:24:21 ℹ️ 🌤 CLUSTER_CLOUD is set with aws
10:24:21 ℹ️ 🗺 CLUSTER_REGION is set with eu-west-3
10:24:21 ℹ️ 💡 if you notice that the playground is using unexpected ccloud details, use to remove all caching and re-launch the example
10:24:24 ℹ️ 🌱 cluster aws is ready to be used!
10:24:26 ℹ️ ❌ Deleting topic users
Error while executing topic command : Topic 'users' does not exist as expected
[2025-12-04 10:24:30,442] ERROR java.lang.IllegalArgumentException: Topic 'users' does not exist as expected
at org.apache.kafka.tools.TopicCommand.ensureTopicExists(TopicCommand.java:214)
at org.apache.kafka.tools.TopicCommand$TopicService.deleteTopic(TopicCommand.java:727)
at org.apache.kafka.tools.TopicCommand.execute(TopicCommand.java:115)
at org.apache.kafka.tools.TopicCommand.mainNoExit(TopicCommand.java:92)
at org.apache.kafka.tools.TopicCommand.main(TopicCommand.java:87)
(org.apache.kafka.tools.TopicCommand)
redis Pulling
redis-insight Pulling
redis Pulled
redis-insight Pulled
Network fm-redis-sink_default Creating
Network fm-redis-sink_default Created
Container redis Creating
Container redis Created
Container ngrok Creating
Container redis-insight Creating
Container redis-insight Created
Container ngrok Created
Container redis Starting
Container redis Started
Container ngrok Starting
Container redis-insight Starting
Container redis-insight Started
Container ngrok Started
10:24:41 ℹ️ Waiting for ngrok to start
10:24:41 ℹ️ Getting ngrok hostname and port
10:24:41 ℹ️ NGROK_PORT is not a valid number, keep retrying...
10:24:41 ℹ️ Getting ngrok hostname and port
10:24:41 ℹ️ NGROK_PORT is not a valid number, keep retrying...
10:24:41 ℹ️ Getting ngrok hostname and port
10:24:41 ℹ️ NGROK_PORT is not a valid number, keep retrying...
10:24:41 ℹ️ Getting ngrok hostname and port
10:24:41 ℹ️ NGROK_PORT is not a valid number, keep retrying...
10:24:41 ℹ️ Getting ngrok hostname and port
10:24:41 ℹ️ NGROK_PORT is not a valid number, keep retrying...
10:24:41 ℹ️ Getting ngrok hostname and port
10:24:41 ℹ️ Sending messages to topic users
10:24:43 ℹ️ 📢 key no known schema could be identified, payload will be sent as raw data
10:24:43 ℹ️ 📢 value no known schema could be identified, payload will be sent as raw data
10:24:43 ℹ️ ✨ generating key data...
10:24:43 ℹ️ 💫 payload is not single json, one record per line will be sent
10:24:43 ℹ️ ✨ generating value data...
10:24:43 ℹ️ 💫 payload is not single json, one record per line will be sent
10:24:43 ℹ️ 🗝️ key key1 is set with a number 1, it will be used as starting point
10:24:43 ℹ️ ✨ 3 records were generated
key1|value1
key2|value2
key3|value3
10:24:45 ℹ️ 📤 producing 3 records to topic users
[2025-12-04 10:24:48,453] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 1 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:49,666] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 5 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:50,019] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 6 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:50,557] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 7 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:51,574] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 8 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:52,604] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 9 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:53,724] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 10 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:54,843] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 11 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:55,887] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 12 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:57,005] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 13 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:58,125] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 14 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:24:59,243] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 15 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:00,344] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 16 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:01,464] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 17 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:02,583] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 18 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:03,701] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 19 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:04,822] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 20 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:05,942] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 21 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:07,065] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 22 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:08,184] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 23 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:09,303] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 24 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:10,423] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 25 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:11,543] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 26 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:12,708] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 27 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:13,828] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 28 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:14,950] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 29 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:16,069] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 30 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:17,188] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 31 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:18,307] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 32 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:19,427] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 33 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:20,419] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 34 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:21,503] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 35 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:22,623] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 36 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:23,742] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 37 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:24,862] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 38 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:25,980] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 39 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:27,099] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 40 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:28,222] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 41 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:29,341] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 42 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:30,434] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 43 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:31,554] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 44 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:32,678] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 45 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:33,798] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 46 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:34,918] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 47 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:36,039] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 48 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:37,158] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 49 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:38,278] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 50 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:39,387] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 51 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:40,506] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 52 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:41,625] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 53 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:42,744] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 54 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:43,863] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 55 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:44,977] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 56 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:46,097] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 57 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:46,936] ERROR Error when sending message to topic users with key: 4 bytes, value: 6 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
org.apache.kafka.common.errors.TimeoutException: Topic users not present in metadata after 60000 ms.
Caused by: org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition.
[2025-12-04 10:25:47,216] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 58 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:48,336] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 59 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:49,455] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 60 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:50,576] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 61 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:51,695] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 62 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:52,815] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 63 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:53,934] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 64 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:54,975] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 65 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:56,093] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 66 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:57,213] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 67 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:58,332] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 68 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:25:59,452] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 69 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:00,572] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 70 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:01,691] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 71 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:02,811] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 72 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:03,901] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 73 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:05,020] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 74 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:06,137] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 75 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:07,257] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 76 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:08,375] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 77 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:09,494] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 78 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:10,548] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 79 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:11,668] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 80 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:12,786] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 81 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:13,872] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 82 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:14,994] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 83 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:15,991] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 84 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:17,109] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 85 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:18,193] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 86 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:19,305] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 87 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:20,425] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 88 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:21,545] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 89 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:22,665] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 90 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:23,784] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 91 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:24,904] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 92 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:26,023] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 93 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:27,143] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 94 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:28,262] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 95 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:29,381] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 96 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:30,500] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 97 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:31,619] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 98 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:32,738] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 99 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:33,858] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 100 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:34,977] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 101 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:36,096] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 102 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:37,216] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 103 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:38,335] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 104 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:39,455] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 105 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:40,574] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 106 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:41,695] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 107 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:42,813] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 108 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:43,934] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 109 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:45,052] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 110 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:46,169] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 111 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:46,942] ERROR Error when sending message to topic users with key: 4 bytes, value: 6 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
org.apache.kafka.common.errors.TimeoutException: Topic users not present in metadata after 60000 ms.
Caused by: org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition.
[2025-12-04 10:26:47,243] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 112 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:48,292] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 113 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:49,412] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 114 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:50,532] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 115 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:51,651] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 116 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:52,769] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 117 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:53,888] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 118 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:55,007] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 119 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:56,126] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 120 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:57,159] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 121 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:58,195] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 122 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:26:59,314] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 123 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:00,434] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 124 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:01,554] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 125 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:02,674] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 126 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:03,793] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 127 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:04,913] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 128 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:06,035] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 129 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:07,140] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 130 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:08,261] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 131 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:09,380] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 132 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:10,499] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 133 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:11,618] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 134 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:12,738] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 135 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:13,857] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 136 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:14,979] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 137 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:16,098] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 138 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:17,217] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 139 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:18,298] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 140 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:19,417] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 141 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:20,520] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 142 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:21,641] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 143 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:22,761] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 144 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:23,880] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 145 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:25,000] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 146 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:26,119] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 147 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:27,239] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 148 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:28,361] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 149 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:29,385] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 150 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:30,504] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 151 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:31,624] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 152 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:32,743] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 153 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:33,863] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 154 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:34,895] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 155 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:36,015] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 156 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:37,135] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 157 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:38,224] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 158 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:39,342] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 159 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:40,460] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 160 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:41,478] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 161 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:42,597] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 162 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:43,661] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 163 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:44,779] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 164 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:45,899] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 165 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2025-12-04 10:27:46,944] ERROR Error when sending message to topic users with key: 4 bytes, value: 6 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
org.apache.kafka.common.errors.TimeoutException: Topic users not present in metadata after 60000 ms.
Caused by: org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition.
[2025-12-04 10:27:47,018] WARN [Producer clientId=console-producer] The metadata response from the cluster reported a recoverable issue with correlation id 166 : {users=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
10:27:47 ℹ️ 📤 produced 3 records to topic users, took: 3min 2sec
10:27:48 ℹ️ Creating fully managed connector
10:27:50 ℹ️ 🛠️ Creating 🌤️🤖fully managed connector RedisSink_runner
10:27:53 ℹ️ ✅ 🌤️🤖fully managed connector RedisSink_runner was successfully created
10:27:55 ℹ️ 🔩 list of all available parameters for 🌤️🤖fully managed connector RedisSink_runner (RedisSink) and version unknown (with default value when applicable)
"auto.restart.on.user.error": "true",
"connector.class": "STRING",
"connector.egress.whitelist": "STRING",
"errors.deadletterqueue.topic.name": "dlq-${connector}",
"errors.tolerance": "all",
"input.data.format": "JSON",
"input.key.format": "STRING",
"kafka.api.key": "STRING",
"kafka.api.secret": "PASSWORD",
"kafka.auth.mode": "KAFKA_API_KEY",
"kafka.service.account.id": "STRING",
"key.converter.key.subject.name.strategy": "TopicNameStrategy",
"max.poll.interval.ms": "300000",
"max.poll.records": "500",
"name": "STRING",
"redis.client.mode": "Standalone",
"redis.database": "0",
"redis.hostname": "STRING",
"redis.password": "PASSWORD",
"redis.portnumber": "INT",
"redis.ssl.keystore.file": "PASSWORD",
"redis.ssl.keystore.password": "PASSWORD",
"redis.ssl.mode": "disabled",
"redis.ssl.truststore.file": "PASSWORD",
"redis.ssl.truststore.password": "PASSWORD",
"schema.context.name": "default",
"tasks.max": "INT",
"topics": "LIST",
"topics.regex": "STRING",
"value.converter.connect.meta.data": "BOOLEAN",
"value.converter.decimal.format": "BASE64",
"value.converter.ignore.default.for.nullables": "false",
"value.converter.reference.subject.name.strategy": "DefaultReferenceSubjectNameStrategy",
"value.converter.replace.null.with.default": "true",
"value.converter.schemas.enable": "false",
"value.converter.value.subject.name.strategy": "TopicNameStrategy",
10:27:58 ℹ️ 🧩 Displaying status for 🌤️🤖fully managed connector RedisSink_runner (lcc-q3dzp2)
Name Status Tasks Stack Trace
###################################################################
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
topics: Topic(s) "users" doesn't exist. validation_errors: topics: Topic(s) "users" doesn't exist.
###################################################################
10:28:00 ℹ️ ⏳ waiting up to 180 seconds for connector RedisSink_runner (lcc-q3dzp2) to be RUNNING
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
🔁
RedisSink_runner ❌ FAILED 🤔 N/A connector: Unable to validate configuration. If an update was made to the configuration, this means that the configuration was invalid, and the connector continues to operate on a previous configuration that passed validation. Errors:
ERROR: Failed after 180 seconds. Please troubleshoot and run again.
10:38:00 🔥 ####################################################
10:38:00 🔥 🔥 RESULT: FAILURE for fully-managed-redis-sink.sh (took: 13min 43sec - )
10:38:00 🔥 ####################################################
10:38:04 ℹ️ 🌐 documentation is available at:
https://docs.confluent.io/cloud/current/connectors/cc-redis-sink.html
10:38:04 🔥 💀 The test fully-managed-redis-sink.sh (default_retry) has failed after 1 attempts.
10:38:04 🔥 ####################################################
10:38:04 🔥 🐳 docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f6b1dec46309 amazon/aws-cli "/usr/local/bin/aws …" 1 second ago Up 1 second heuristic_darwin
9b679f7a1374 redis/redisinsight:latest "./docker-entry.sh n…" 13 minutes ago Up 13 minutes 0.0.0.0:5540->5540/tcp, [::]:5540->5540/tcp redis-insight
cf7b961141c3 ngrok/ngrok:latest "/nix/store/1qpvcjc0…" 13 minutes ago Up 13 minutes 0.0.0.0:4040->4040/tcp, [::]:4040->4040/tcp ngrok
3d0208d5e2cc redis:7.2.4 "docker-entrypoint.s…" 13 minutes ago Up 13 minutes 6379/tcp redis
10:38:04 🔥 ####################################################
10:38:04 🔥 ####################################################
10:38:04 🔥 heuristic_darwin logs
10:38:04 ❗ ####################################################
10:38:04 🔥 ####################################################
10:38:04 🔥 redis-insight logs
10:38:04 ❗ ####################################################
10:38:04 🔥 ####################################################
10:38:04 🔥 ngrok logs
10:38:04 ❗ ####################################################
10:38:04 🔥 ####################################################
10:38:04 🔥 redis logs
10:38:04 ❗ ####################################################