Wondering if anyone has seen this behavior and how to resolve it…
Using Confluent Cloud , with local (windows 10) CLI install.
Been through the demos, all works well, for a while. After producing and consuming a good number of messages, I left the command windows open. Coming back later that afternoon, I found that attempts to connect to either produce or consume resulted in:
an apparent timeout after 2 minutes when connecting to consume (the time was consistent), the message was “Error - can’t connect to cluster”
no progress when trying to produce (no error message)
All other commands appeared to still work. I could list the cluster, the api keys, etc… just couldn’t produce/consume… as if the api-key to the SR was no longer valid, but there were no obvious errors, other than the eventual “Can’t connect”).
The first time it happened, opening a new command window resolved the issue. Since then, even that does not work.
ccloud - Confluent Cloud CLI
Git Ref: b9ca3f7e
Build Date: 2021-09-07T23:37:20Z
Go Version: go1.16.3 (windows/amd64)
I believe rebooting will resolve the problem, but for how long? I can’t even say what period of inactivity is required to cause the problem to happen.
Any advice/feedback welcomed.