You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other commands work just fine, such as topicctl get members. I know that the SASL user I am using to fetch the details does have the right permissions to read this information, since I was able to use the regular kafka-consumer-groups.sh script as well as a custom script based off of sarama's library to read consumer offsets. I can also use topicctl tail to read data from the topic in question.
The kafka cluster I am interacting with is hosted in AWS eu-central-1, running Kafka version 3.6.0. I am using topicctl version v1.18.0 (ref:dev).
Can you try providing --conn-timeout with a larger value? get lags fetches messages which can timeout easily, especially when running against t3.small MSK instances
When attempting to fetch consumer lags via
topicctl get lags
, I am getting the following error:Other commands work just fine, such as
topicctl get members
. I know that the SASL user I am using to fetch the details does have the right permissions to read this information, since I was able to use the regularkafka-consumer-groups.sh
script as well as a custom script based off ofsarama
's library to read consumer offsets. I can also usetopicctl tail
to read data from the topic in question.The kafka cluster I am interacting with is hosted in AWS eu-central-1, running Kafka version 3.6.0. I am using
topicctl version v1.18.0 (ref:dev)
.Debug logs:
The text was updated successfully, but these errors were encountered: