divijvaidya commented on code in PR #578:
URL: https://github.com/apache/kafka-site/pull/578#discussion_r1494668977
##########
blog.html:
##########
@@ -22,6 +22,125 @@
<!--#include virtual="includes/_nav.htm" -->
<div class="right">
<h1 class="content-title">Blog</h1>
+ <article>
+ <h2 class="bullet">
+ <a id="apache_kafka_370_release_announcement"></a>
+ <a href="#apache_kafka_370_release_announcement">Apache
Kafka 3.7.0 Release Announcement</a>
+ </h2>
+ February 2024 - Stanislav Kozlovski (<a
href="https://twitter.com/BdKozlovski";>@BdKozlovski</a>)
+ <p>We are proud to announce the release of Apache Kafka 3.7.0.
This release contains many new features and improvements. This blog post will
highlight some of the more prominent features. For a full list of changes, be
sure to check the <a
href="https://downloads.apache.org/kafka/3.7.0/RELEASE_NOTES.html";>release
notes</a>.</p>
+ <p>See the <a
href="https://kafka.apache.org/36/documentation.html#upgrade_3_7_0";>Upgrading
to 3.7.0 from any version 0.8.x through 3.6.x</a> section in the documentation
for the list of notable changes and detailed upgrade steps.</p>
+ <p>
+ In the last release, 3.6,
+ <a
href="https://kafka.apache.org/documentation/#kraft_zk_migration";>the ability
to migrate Kafka clusters from a ZooKeeper metadata system</a>
+ to a KRaft metadata system was ready for usage in
production environments with one caveat -- JBOD was not yet available for KRaft
clusters.
+ In this release, we are shipping an early access release
of JBOD in KRaft. (See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>KIP-858</a>
for details)
+ </p>
+ <p>
+ Additionally, client APIs released prior to Apache Kafka
2.1 are now marked deprecated in 3.7 and will be removed in Apache Kafka 4.0.
See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0";>KIP-896</a>
for details and RPC versions that are now deprecated.
+ </p>
+ <p>
+ Java 11 support for the Kafka broker is also marked
deprecated in 3.7, and is planned to be removed in Kafka 4.0. See <a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510";>KIP-1013</a>
for more details
Review Comment:
Just to make this more clear, could we add a sentence here: "Note that
clients can continue to use JDK >= 8 to connect to Kafka brokers."
##########
blog.html:
##########
@@ -22,6 +22,125 @@
<!--#include virtual="includes/_nav.htm" -->
<div class="right">
<h1 class="content-title">Blog</h1>
+ <article>
+ <h2 class="bullet">
+ <a id="apache_kafka_370_release_announcement"></a>
+ <a href="#apache_kafka_370_release_announcement">Apache
Kafka 3.7.0 Release Announcement</a>
+ </h2>
+ February 2024 - Stanislav Kozlovski (<a
href="https://twitter.com/BdKozlovski";>@BdKozlovski</a>)
+ <p>We are proud to announce the release of Apache Kafka 3.7.0.
This release contains many new features and improvements. This blog post will
highlight some of the more prominent features. For a full list of changes, be
sure to check the <a
href="https://downloads.apache.org/kafka/3.7.0/RELEASE_NOTES.html";>release
notes</a>.</p>
+ <p>See the <a
href="https://kafka.apache.org/36/documentation.html#upgrade_3_7_0";>Upgrading
to 3.7.0 from any version 0.8.x through 3.6.x</a> section in the documentation
for the list of notable changes and detailed upgrade steps.</p>
+ <p>
+ In the last release, 3.6,
+ <a
href="https://kafka.apache.org/documentation/#kraft_zk_migration";>the ability
to migrate Kafka clusters from a ZooKeeper metadata system</a>
+ to a KRaft metadata system was ready for usage in
production environments with one caveat -- JBOD was not yet available for KRaft
clusters.
+ In this release, we are shipping an early access release
of JBOD in KRaft. (See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>KIP-858</a>
for details)
+ </p>
+ <p>
+ Additionally, client APIs released prior to Apache Kafka
2.1 are now marked deprecated in 3.7 and will be removed in Apache Kafka 4.0.
See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0";>KIP-896</a>
for details and RPC versions that are now deprecated.
+ </p>
+ <p>
+ Java 11 support for the Kafka broker is also marked
deprecated in 3.7, and is planned to be removed in Kafka 4.0. See <a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510";>KIP-1013</a>
for more details
+ </p>
+ <p>
+ <i>Note: ZooKeeper is marked as deprecated since the 3.5.0
release. ZooKeeper is planned to be removed in Apache Kafka 4.0. For more
information, please see the documentation for <a
href="https://kafka.apache.org/documentation/#zk_depr";>ZooKeeper
Deprecation</a></i>.
+ </p>
+
+ <h3>Kafka Broker, Controller, Producer, Consumer and Admin
Client</h3>
+ <ul>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>(Early
Access) KIP-858 Handle JBOD broker disk failure in KRaft</a>:
+ </b><br>This update closes the gap on one of the last
major missing features in KRaft by adding JBOD support in KRaft-based clusters.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-714%3A+Client+metrics+and+observability";>KIP-714
Client metrics and observability</a>:
+ </b><br>With KIP-714, operators get better visibility
into the clients connecting to their cluster with broker-side support of
client-level metrics via a standardized telemetry interface.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-1000%3A+List+Client+Metrics+Configuration+Resources";>KIP-1000
List Client Metrics Configuration Resources</a>:
+ </b><br>KIP-1000 supports KIP-714 by introducing a way
to create, read, update, and delete the client metrics configuration resources
using the existing RPCs and the kafka-configs.sh tool.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-848%3A+The+Next+Generation+of+the+Consumer+Rebalance+Protocol";>(Early
Access) KIP-848 The Next Generation of the Consumer Rebalance Protocol</a>:
+ </b><br>The new simplified Consumer Rebalance Protocol
moves complexity away from the consumer and into the Group Coordinator within
the broker and completely revamps the protocol to be incremental in nature. It
provides the same guarantee as the current protocol––but better and more
efficient, including no longer relying on a global synchronization barrier. <a
href="https://cwiki.apache.org/confluence/display/KAFKA/The+Next+Generation+of+the+Consumer+Rebalance+Protocol+%28KIP-848%29+-+Early+Access+Release+Notes";>See
the early access release notes for more information.</a>
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-951%3A+Leader+discovery+optimisations+for+the+client";>KIP-951
Leader discovery optimisations for the client</a>:
+ </b><br>KIP-951 optimizes the time it takes for a
client to discover the new leader of a partition, leading to reduced end-to-end
latency of produce/fetch requests in the presence of leadership changes (broker
restarts, partition reassignments, etc.).
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-975%3A+Docker+Image+for+Apache+Kafka";>KIP-975
Docker Image for Apache Kafka</a>:
+ </b><br>Introduces a <a
href="https://docs.docker.com/trusted-content/dsos-program/";>Sponsored OSS</a>
Apache Kafka Docker image, enabling quicker testing and deployment, as well as
onboarding of developers.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-580%3A+Exponential+Backoff+for+Kafka+Clients";>KIP-580
Exponential Backoff for Kafka Clients</a>:
+ </b><br>Changes the client’s retry backoff time used
for retrying failed requests from a static one to an exponentially-increasing
one. This should help reduce slow metadata convergence after broker failure due
to overload.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-963%3A+Additional+metrics+in+Tiered+Storage";>KIP-963
Additional metrics in Tiered Storage</a>:
+ </b><br>KIP-405 brought the early access of Tiered
Storage, and with this update we’re introducing new metrics for the feature,
allowing you to better monitor performance, troubleshoot, and prevent issues.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-979%3A+Allow+independently+stop+KRaft+processes";>KIP-979
Allow independently stop KRaft processes</a>:
+ </b><br>Adds a way to independently stop KRaft
processes in cases where operators are running in combined mode (a controller
and broker in the same node). Previously, you could only stop both. The command
line for stopping Kafka nodes now includes a pair of optional and mutually
exclusive parameters "[--process-role]" OR "[--node-id]" to use with
./bin/kafka-server-stop.sh.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-890%3A+Transactions+Server-Side+Defense";>KIP-890
Transactions Server-Side Defense</a>:
+ </b><br>Another part of this KIP shipped, this time
adding transaction verification preventing hanging transactions for consumer
offset partitions.
+ </li>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0";>KIP-896
Remove old client protocol API versions in Kafka 4.0</a>:
Review Comment:
are missing KIP-1013 here?
##########
blog.html:
##########
@@ -22,6 +22,125 @@
<!--#include virtual="includes/_nav.htm" -->
<div class="right">
<h1 class="content-title">Blog</h1>
+ <article>
+ <h2 class="bullet">
+ <a id="apache_kafka_370_release_announcement"></a>
+ <a href="#apache_kafka_370_release_announcement">Apache
Kafka 3.7.0 Release Announcement</a>
+ </h2>
+ February 2024 - Stanislav Kozlovski (<a
href="https://twitter.com/BdKozlovski";>@BdKozlovski</a>)
+ <p>We are proud to announce the release of Apache Kafka 3.7.0.
This release contains many new features and improvements. This blog post will
highlight some of the more prominent features. For a full list of changes, be
sure to check the <a
href="https://downloads.apache.org/kafka/3.7.0/RELEASE_NOTES.html";>release
notes</a>.</p>
+ <p>See the <a
href="https://kafka.apache.org/36/documentation.html#upgrade_3_7_0";>Upgrading
to 3.7.0 from any version 0.8.x through 3.6.x</a> section in the documentation
for the list of notable changes and detailed upgrade steps.</p>
+ <p>
+ In the last release, 3.6,
+ <a
href="https://kafka.apache.org/documentation/#kraft_zk_migration";>the ability
to migrate Kafka clusters from a ZooKeeper metadata system</a>
+ to a KRaft metadata system was ready for usage in
production environments with one caveat -- JBOD was not yet available for KRaft
clusters.
+ In this release, we are shipping an early access release
of JBOD in KRaft. (See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>KIP-858</a>
for details)
+ </p>
+ <p>
+ Additionally, client APIs released prior to Apache Kafka
2.1 are now marked deprecated in 3.7 and will be removed in Apache Kafka 4.0.
See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0";>KIP-896</a>
for details and RPC versions that are now deprecated.
+ </p>
+ <p>
+ Java 11 support for the Kafka broker is also marked
deprecated in 3.7, and is planned to be removed in Kafka 4.0. See <a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510";>KIP-1013</a>
for more details
+ </p>
+ <p>
+ <i>Note: ZooKeeper is marked as deprecated since the 3.5.0
release. ZooKeeper is planned to be removed in Apache Kafka 4.0. For more
information, please see the documentation for <a
href="https://kafka.apache.org/documentation/#zk_depr";>ZooKeeper
Deprecation</a></i>.
+ </p>
+
+ <h3>Kafka Broker, Controller, Producer, Consumer and Admin
Client</h3>
+ <ul>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>(Early
Access) KIP-858 Handle JBOD broker disk failure in KRaft</a>:
Review Comment:
AFAIK, we haven't officially defined the meaning for "Early access" in our
community. It is very confusing to users on what it means. A nice explanation
on what it means (not recommended to use in production), would be very nice.
##########
blog.html:
##########
@@ -22,6 +22,125 @@
<!--#include virtual="includes/_nav.htm" -->
<div class="right">
<h1 class="content-title">Blog</h1>
+ <article>
+ <h2 class="bullet">
+ <a id="apache_kafka_370_release_announcement"></a>
+ <a href="#apache_kafka_370_release_announcement">Apache
Kafka 3.7.0 Release Announcement</a>
+ </h2>
+ February 2024 - Stanislav Kozlovski (<a
href="https://twitter.com/BdKozlovski";>@BdKozlovski</a>)
+ <p>We are proud to announce the release of Apache Kafka 3.7.0.
This release contains many new features and improvements. This blog post will
highlight some of the more prominent features. For a full list of changes, be
sure to check the <a
href="https://downloads.apache.org/kafka/3.7.0/RELEASE_NOTES.html";>release
notes</a>.</p>
+ <p>See the <a
href="https://kafka.apache.org/36/documentation.html#upgrade_3_7_0";>Upgrading
to 3.7.0 from any version 0.8.x through 3.6.x</a> section in the documentation
for the list of notable changes and detailed upgrade steps.</p>
+ <p>
+ In the last release, 3.6,
+ <a
href="https://kafka.apache.org/documentation/#kraft_zk_migration";>the ability
to migrate Kafka clusters from a ZooKeeper metadata system</a>
+ to a KRaft metadata system was ready for usage in
production environments with one caveat -- JBOD was not yet available for KRaft
clusters.
+ In this release, we are shipping an early access release
of JBOD in KRaft. (See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>KIP-858</a>
for details)
+ </p>
+ <p>
+ Additionally, client APIs released prior to Apache Kafka
2.1 are now marked deprecated in 3.7 and will be removed in Apache Kafka 4.0.
See <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0";>KIP-896</a>
for details and RPC versions that are now deprecated.
+ </p>
+ <p>
+ Java 11 support for the Kafka broker is also marked
deprecated in 3.7, and is planned to be removed in Kafka 4.0. See <a
href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789510";>KIP-1013</a>
for more details
+ </p>
+ <p>
+ <i>Note: ZooKeeper is marked as deprecated since the 3.5.0
release. ZooKeeper is planned to be removed in Apache Kafka 4.0. For more
information, please see the documentation for <a
href="https://kafka.apache.org/documentation/#zk_depr";>ZooKeeper
Deprecation</a></i>.
+ </p>
+
+ <h3>Kafka Broker, Controller, Producer, Consumer and Admin
Client</h3>
+ <ul>
+ <li><b><a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>(Early
Access) KIP-858 Handle JBOD broker disk failure in KRaft</a>:
+ </b><br>This update closes the gap on one of the last
major missing features in KRaft by adding JBOD support in KRaft-based clusters.
Review Comment:
should we also update
https://kafka.apache.org/37/documentation/#kraft_missing?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
