This is an automated email from the ASF dual-hosted git repository.
ijuma pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new 7b49f175b96 MINOR: Add upgrade note regarding the Strictly Uniform
Sticky Partitioner (KIP-794) (#12630)
7b49f175b96 is described below
commit 7b49f175b964c468d5ca7ac9bd70dfd72e6a2e4e
Author: Artem Livshits <84364232+artemlivsh...@users.noreply.github.com>
AuthorDate: Tue Sep 13 11:56:44 2022 -0700
MINOR: Add upgrade note regarding the Strictly Uniform Sticky Partitioner
(KIP-794) (#12630)
Reviewers: Ismael Juma <ism...@juma.me.uk>, David Jacot
<dja...@confluent.io>
---
docs/upgrade.html | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/docs/upgrade.html b/docs/upgrade.html
index e484a2ad679..9ac1eccdb2c 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -81,6 +81,11 @@
<h5><a id="upgrade_330_notable" href="#upgrade_330_notable">Notable changes in
3.3.0</a></h5>
<ul>
+ <li>The partitioner used by default for records with no keys has been
improved to avoid pathological behavior when one or more brokers are slow.
+ The new logic may affect the batching behavior, which can be tuned
using the <code>batch.size</code> and/or <code>linger.ms</code> configuration
settings.
+ The previous behavior can be restored by setting
<code>partitioner.class=org.apache.kafka.clients.producer.internals.DefaultPartitioner</code>.
+ See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-794%3A+Strictly+Uniform+Sticky+Partitioner";>KIP-794</a>
for more details.
+ </li>
<li>There is now a slightly different upgrade process for KRaft
clusters than for ZK-based clusters, as described above.</li>
<li>Introduced a new API <code>addMetricIfAbsent</code> to
<code>Metrics</code> which would create a new Metric if not existing or return
the same metric
if already registered. Note that this behaviour is different from
<code>addMetric</code> API which throws an
<code>IllegalArgumentException</code> when
