Repository: kafka Updated Branches: refs/heads/0.10.2 ff50cf9ea -> a00823805
KAFKA-4869; Update 0.10.2.0 upgrade notes Author: Manikumar Reddy <manikumar.re...@gmail.com> Reviewers: Ismael Juma <ism...@juma.me.uk> Closes #3735 from omkreddy/cleanup10 Project: http://git-wip-us.apache.org/repos/asf/kafka/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/a0082380 Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/a0082380 Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/a0082380 Branch: refs/heads/0.10.2 Commit: a008238051b3dbb1a85c0c04b31bbbb486cd7fac Parents: ff50cf9 Author: Manikumar Reddy <manikumar.re...@gmail.com> Authored: Fri Aug 25 11:22:16 2017 +0100 Committer: Ismael Juma <ism...@juma.me.uk> Committed: Fri Aug 25 11:22:16 2017 +0100 ---------------------------------------------------------------------- docs/upgrade.html | 1 - 1 file changed, 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka/blob/a0082380/docs/upgrade.html ---------------------------------------------------------------------- diff --git a/docs/upgrade.html b/docs/upgrade.html index 0221f63..d7581fa 100644 --- a/docs/upgrade.html +++ b/docs/upgrade.html @@ -87,7 +87,6 @@ Kafka cluster before upgrading your clients. Version 0.10.2 brokers support 0.8. should not be set in the Streams app any more. If the Kafka cluster is secured, Streams apps must have the required security privileges to create new topics.</li> <li>Several new fields including "security.protocol", "connections.max.idle.ms", "retry.backoff.ms", "reconnect.backoff.ms" and "request.timeout.ms" were added to StreamsConfig class. User should pay attention to the default values and set these if needed. For more details please refer to <a href="/{{version}}/documentation/#streamsconfigs">3.5 Kafka Streams Configs</a>.</li> - <li>The <code>offsets.topic.replication.factor</code> broker config is now enforced upon auto topic creation. Internal auto topic creation will fail with a GROUP_COORDINATOR_NOT_AVAILABLE error until the cluster size meets this replication factor requirement.</li> </ul> <h5><a id="upgrade_1020_new_protocols" href="#upgrade_1020_new_protocols">New Protocol Versions</a></h5>
