Repository: kafka-site Updated Branches: refs/heads/asf-site 4ac323afc -> b8a407363
upgrade notes for 0.10.2.1 Project: http://git-wip-us.apache.org/repos/asf/kafka-site/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka-site/commit/b8a40736 Tree: http://git-wip-us.apache.org/repos/asf/kafka-site/tree/b8a40736 Diff: http://git-wip-us.apache.org/repos/asf/kafka-site/diff/b8a40736 Branch: refs/heads/asf-site Commit: b8a4073634b7d4cea03f9c063e72e93bbc04b6a6 Parents: 4ac323a Author: Gwen Shapira <csh...@gmail.com> Authored: Tue Apr 11 17:41:05 2017 -0700 Committer: Gwen Shapira <csh...@gmail.com> Committed: Tue Apr 11 17:41:05 2017 -0700 ---------------------------------------------------------------------- 0102/generated/topic_config.html | 4 ++-- 0102/streams.html | 7 +++++++ 0102/upgrade.html | 10 +++++++++- 3 files changed, 18 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka-site/blob/b8a40736/0102/generated/topic_config.html ---------------------------------------------------------------------- diff --git a/0102/generated/topic_config.html b/0102/generated/topic_config.html index 33f61d0..1f7b355 100644 --- a/0102/generated/topic_config.html +++ b/0102/generated/topic_config.html @@ -21,11 +21,11 @@ <tr> <td>flush.ms</td><td>This setting allows specifying a time interval at which we will force an fsync of data written to the log. For example if this was set to 1000 we would fsync after 1000 ms had passed. In general we recommend you not set this and use replication for durability and allow the operating system's background flush capabilities as it is more efficient.</td><td>long</td><td>9223372036854775807</td><td>[0,...]</td><td>log.flush.interval.ms</td><td>medium</td></tr> <tr> -<td>follower.replication.throttled.replicas</td><td>A list of replicas for which log replication should be throttled on the follower side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.</td><td>list</td><td>""</td><td>kafka.server.ThrottledReplicaListValidator$@1d6946d4</td><td>follower.replication.throttled.replicas</td><td>medium</td></tr> +<td>follower.replication.throttled.replicas</td><td>A list of replicas for which log replication should be throttled on the follower side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.</td><td>list</td><td>""</td><td>kafka.server.ThrottledReplicaListValidator$@6121c9d6</td><td>follower.replication.throttled.replicas</td><td>medium</td></tr> <tr> <td>index.interval.bytes</td><td>This setting controls how frequently Kafka adds an index entry to it's offset index. The default setting ensures that we index a message roughly every 4096 bytes. More indexing allows reads to jump closer to the exact position in the log but makes the index larger. You probably don't need to change this.</td><td>int</td><td>4096</td><td>[0,...]</td><td>log.index.interval.bytes</td><td>medium</td></tr> <tr> -<td>leader.replication.throttled.replicas</td><td>A list of replicas for which log replication should be throttled on the leader side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.</td><td>list</td><td>""</td><td>kafka.server.ThrottledReplicaListValidator$@1d6946d4</td><td>leader.replication.throttled.replicas</td><td>medium</td></tr> +<td>leader.replication.throttled.replicas</td><td>A list of replicas for which log replication should be throttled on the leader side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.</td><td>list</td><td>""</td><td>kafka.server.ThrottledReplicaListValidator$@6121c9d6</td><td>leader.replication.throttled.replicas</td><td>medium</td></tr> <tr> <td>max.message.bytes</td><td>This is largest message size Kafka will allow to be appended. Note that if you increase this size you must also increase your consumer's fetch size so they can fetch messages this large.</td><td>int</td><td>1000012</td><td>[0,...]</td><td>message.max.bytes</td><td>medium</td></tr> <tr> http://git-wip-us.apache.org/repos/asf/kafka-site/blob/b8a40736/0102/streams.html ---------------------------------------------------------------------- diff --git a/0102/streams.html b/0102/streams.html index 2b4c441..fe0e84e 100644 --- a/0102/streams.html +++ b/0102/streams.html @@ -813,6 +813,13 @@ $ java -cp path-to-app-fatjar.jar com.example.MyStreamsApp See <a href="#streams_api_changes_0101">below</a> a complete list of 0.10.1 API changes that allow you to advance your application and/or simplify your code base, including the usage of new features. </p> + <h3><a id="streams_api_changes_01021" href="#streams_api_changes_0102">Notable changes in 0.10.2.1</a></h3> + <p> + Parameter updates in <code>StreamsConfig</code>: + </p> + <ul> + <li> of particular importance to improve the resiliency of a Kafka Streams application are two changes to default parameters of producer <code>retries</code> and consumer <code>max.poll.interval.ms</code> </li> + </ul> <h3><a id="streams_api_changes_0102" href="#streams_api_changes_0102">Streams API changes in 0.10.2.0</a></h3> <p> http://git-wip-us.apache.org/repos/asf/kafka-site/blob/b8a40736/0102/upgrade.html ---------------------------------------------------------------------- diff --git a/0102/upgrade.html b/0102/upgrade.html index 58754dd..12bd90e 100644 --- a/0102/upgrade.html +++ b/0102/upgrade.html @@ -61,6 +61,14 @@ Kafka cluster before upgrading your clients. Version 0.10.2 brokers support 0.8. <li> See <a href="/{{version}}/documentation/streams#streams_api_changes_0102">Streams API changes in 0.10.2</a> for more details. </li> </ul> +<h5><a id="upgrade_10201_notable" href="#upgrade_10201_notable">Notable changes in 0.10.2.1</a></h5> +<ul> + <li> The default values for two configurations of the StreamsConfig class were changed to improve the resiliency of Kafka Streams applications. The internal Kafka Streams producer <code>retries</code> default value was changed from 0 to 10. The internal Kafka Streams consumer <code>max.poll.interval.ms</code> default value was changed from 300000 to <code>Integer.MAX_VALUE<code>. + </li> +</ul> + + + <h5><a id="upgrade_1020_notable" href="#upgrade_1020_notable">Notable changes in 0.10.2.0</a></h5> <ul> <li>The Java clients (producer and consumer) have acquired the ability to communicate with older brokers. Version 0.10.2 clients @@ -346,4 +354,4 @@ Release 0.7 is incompatible with newer releases. Major changes were made to the </script> -<div class="p-upgrade"></div> \ No newline at end of file +<div class="p-upgrade"></div>
