Kafkamanager support for kafka 2.3.1 version
See original GitHub issueWe just deployed a new kafkacluster with 2.3.1 version. Trying to add the cluster in kafkamamager ,versions are till only 2.2.0. Tried configuring it with 2.2.0. Comes back with
“Yikes! Ask timed out on [ActorSelection[Anchor(akka://kafka-manager-system/), Path(/user/kafka-manager/kafka53/kafka-state)]] after [2000 ms]. Message of type [kafka.manager.model.ActorModel$KSGetBrokers$] was sent by [Actor[akka://kafka-manager-system/user/kafka-manager/kafka53#-1669570313]]. A typical reason for AskTimeoutException
is that the recipient actor didn’t send a reply.”
Is kafkamanager currently supporting this version? Any update would be helpful. Thanks
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5
Top Results From Across the Web
Release Notes - Kafka - Version 2.3.1
Release Notes - Kafka - Version 2.3.1. Below is a summary of the JIRA issues addressed in the 2.3.1 release of Kafka. For...
Read more >The Ultimate UI Tool for Kafka - Offset Explorer
To download the Offset Explorer (formerly Kafka Tool) for your operating system, ... Offset Explorer supports Apache Kafka ® version 0.8.1 and above....
Read more >Amazon MSK adds support for Apache Kafka version 2.3.1
Amazon MSK adds support for Apache Kafka version 2.3.1 ... Amazon MSK is a fully managed service for Apache Kafka that makes it...
Read more >Eco Kafka Manager - EPAM SolutionsHub
Eco Kafka Manager is a tool for monitoring and managing Apache Kafka. While an existing Kafka cluster toolkit lacks an accelerator allowing administrators ......
Read more >node-red-contrib-kafka-manager 0.5.1
Version. 0.5.0 add consumer wildcard topics + topics / to . along with fix on to/from/json. 0.4.3 add convert message ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Getting the same with Kafka 2.4.0 and manager 2.0.0.2. I think it is caused by change in “Consumer Instance Owner” on the brokers.
Got same error, but I think my problem is related to the API version 3 not being supported. From logs: