@Abhishek Reddy Chamakura This is a known issue which got fixed recently. Please change your storm-kafka dependency to the following and give it a try. <dependency> <groupId>org.apache.storm</groupId> <artifactId>storm-kafka</artifactId> <version>1.0.1.2.5.3.0-37</version> </dependency> ... View more

@Dhiraj Sardana This is a known issue which got fixed recently. Please change your storm-kafka dependency to the following and give it a try. <dependency> <groupId>org.apache.storm</groupId> <artifactId>storm-kafka</artifactId> <version>1.0.1.2.5.3.0-37</version> </dependency> ... View more

@amankumbare can you make sure you are passing the zookeeper root as well to your kafka-topics.sh. It should look like this ./bin/kafka-topics.sh --zookeeper node1.example.com:2181,node2.example.com:2181,node1.example.com:2181/kafka --topic name_of_topic --partitions 2 --replication-factor 2 --create ... View more

@Davide Vergari This might be the side effect of several things. We did a shading of all the storm dependencies so that topologies can bring their own version of common dependencies and storm libs wouldn't conflict with the user's topology dependencies. easy fix would be to add to your topology following dependency <dependency> <groupId>org.apache.curator</groupId> <artifactId>curator-framework</artifactId> <version>2.10.0</version> <exclusions> <exclusion> <groupId>log4j</groupId> <artifactId>log4j</artifactId> </exclusion> <exclusion> <groupId>org.jboss.netty</groupId> <artifactId>netty</artifactId> </exclusion> </exclusions> </dependency> ... View more

Kafka MirrorMaker is designed for the sole purpose of replicating kafka's topi cdata from one data center to another. Pros: 1. Simple to setup 2. Uses Kafka's produce and consumer api. Makes it easier to enable wire-encryption(SSL) and Keberos (Nifi can offer the same as they both use the same API). 3. Designed to replicate all the topics in source to target data center . Users can also choose and pick specific topic if they desired so. Cons: 1. Hard to monitor. As the mirror maker is just a JVM process ,provisioning and monitoring the mirror maker process can be hard. One need to monitor the metrics coming from mirrormaker to see if there is any lag or no data being produced into target cluster. 2. MirrorMakers won't keep the origin Kafka topic offsets into target cluster ( Nifi or any other solution will run into the same limitation). As writing a new message into the target data center creates a new offset. ... View more

@Geetha Anne can you post your topology pom.xml and the kafka dependency. Are you sure you are using HDP kafka dependencies in your topology? ... View more

@Shun Takebayashi We will be backporting it for next maint release fro 2.3 and 2.4 ... View more