CDH 6 includes Apache Kafka as part of the core package. The documentation includes improved contents for how to set up, install, and administer your Kafka ecosystem. For more information, see the Cloudera Enterprise 6.0.x Apache Kafka Guide. We look forward to your feedback on both the existing and new documentation.
Issues Fixed in CDK 2.1.1 Powered By Apache Kafka
- KAFKA-724: Allow automatic socket.send.buffer from operating system in SocketServer
- KAFKA-2684: Add force option to topic / config command so they can be called programatically
- KAFKA-2720: Expire group metadata when all offsets have expired
- KAFKA-2948: Remove unused topics from producer metadata set
- KAFKA-3111: Fix ConsumerPerformance reporting to use time-based instead of message-based intervals
- KAFKA-3158: ConsumerGroupCommand should tell whether group is actually dead
- KAFKA-3175: Topic not accessible after deletion even when delete.topic.enable is disabled
- KAFKA-3501: Console consumer process hangs on exit
- KAFKA-3562: Handle topic deletion during a send
- KAFKA-3645: Fix ConsumerGroupCommand and ConsumerOffsetChecker to correctly read endpoint info from ZK
- KAFKA-3716: Validate all timestamps are not negative
- KAFKA-3719: Allow underscores in hostname
- KAFKA-3748: Add consumer-property to console tools consumer
- KAFKA-3774: Make 'time' an optional argument of GetOffsetShell
- KAFKA-3810: replication of internal topics should not be limited by replica.fetch.max.bytes
- KAFKA-3934: Start scripts enable GC by default with no way to disable
- KAFKA-3965: MirrorMaker should not commit offset when exception is thrown from producer.send
- KAFKA-4158: Reset quota to default value if quota override is deleted
- KAFKA-4229: Controller can't start after several zk expired event
- KAFKA-4319: Parallelize shutdown of fetchers in AbstractFetcherManager to speedup shutdown
- KAFKA-4360: Controller may deadLock when autoLeaderRebalance encounter ZK expired
- KAFKA-4428: Kafka does not exit if port is already bound