From f2d4ed5bc4c2bc2bf7241ad6b6a9d3c0ce026269 Mon Sep 17 00:00:00 2001 From: Ismael Juma Date: Thu, 21 Jan 2016 11:44:44 -0800 Subject: [PATCH] MINOR: Upgrade note on compacted topics behaviour on receiving message without key Author: Ismael Juma Reviewers: Grant Henke, Guozhang Wang Closes #798 from ijuma/upgrade-notes-unkeyed-messages-to-compacted-topics --- docs/upgrade.html | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/upgrade.html b/docs/upgrade.html index c72395770ed..d8a77194f96 100644 --- a/docs/upgrade.html +++ b/docs/upgrade.html @@ -39,6 +39,7 @@
  • Broker IDs above 1000 are now reserved by default to automatically assigned broker IDs. If your cluster has existing broker IDs above that threshold make sure to increase the reserved.broker.max.id broker configuration property accordingly.
  • Configuration parameter replica.lag.max.messages was removed. Partition leaders will no longer consider the number of lagging messages when deciding which replicas are in sync.
  • Configuration parameter replica.lag.time.max.ms now refers not just to the time passed since last fetch request from replica, but also to time since the replica last caught up. Replicas that are still fetching messages from leaders but did not catch up to the latest messages in replica.lag.time.max.ms will be considered out of sync.
    • +
  • Compacted topics no longer accept messages without key and an exception is thrown by the producer if this is attempted. In 0.8.x, a message without key would cause the log compaction thread to subsequently complain and quit (and stop compacting all compacted topics).
  • MirrorMaker no longer supports multiple target clusters. As a result it will only accept a single --consumer.config parameter. To mirror multiple source clusters, you will need at least one MirrorMaker instance per source cluster, each with its own consumer configuration.
  • Tools packaged under org.apache.kafka.clients.tools.* have been moved to org.apache.kafka.tools.*. All included scripts will still function as usual, only custom code directly importing these classes will be affected.
  • The default Kafka JVM performance options (KAFKA_JVM_PERFORMANCE_OPTS) have been changed in kafka-run-class.sh.