Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
Chapter 1. Features
AMQ Streams 2.2 and subsequent patch releases introduce the features described in this section.
AMQ Streams 2.2 on RHEL is based on Kafka 3.2.3.
To view all the enhancements and bugs that are resolved in this release, see the AMQ Streams Jira project.
1.1. AMQ Streams 2.2.x (Long Term Support)
AMQ Streams 2.2.x is the Long Term Support (LTS) offering for AMQ Streams.
The latest patch release is AMQ Streams 2.2.2. The AMQ Streams product images have changed to version 2.2.2. The supported Kafka version remains at 3.2.3.
For information on the LTS terms and dates, see the AMQ Streams LTS Support Policy.
1.2. Kafka 3.2.3 support
AMQ Streams now supports Apache Kafka version 3.2.3.
AMQ Streams uses Kafka 3.2.3. Only Kafka distributions built by Red Hat are supported.
For upgrade instructions, see AMQ Streams and Kafka upgrades.
Refer to the Kafka 3.1.0, Kafka 3.2.0, Kafka 3.2.1, and Kafka 3.2.3 Release Notes for additional information.
Kafka 3.1.x is supported only for the purpose of upgrading to AMQ Streams 2.2.
For more information on supported versions, see the AMQ Streams Component Details.
Kafka 3.2.3 uses ZooKeeper version 3.6.3, which is the same version as Kafka 3.1.0. We recommend that you perform a rolling update to use the new binaries.
Kafka 3.2.3 provides access to self-managed mode, where Kafka runs without ZooKeeper by utilizing the Raft protocol. Note that self-managed mode is not supported in AMQ Streams.
1.3. Support for IBM Z and LinuxONE architecture
AMQ Streams 2.2 is enabled to run on IBM Z and LinuxONE s390x architecture.
IBM Z and LinuxONE is tested for AMQ Streams running with Kafka and Open JDK 11, on Red Hat Enterprise Linux 8 and later.
1.3.1. Requirements for IBM Z and LinuxONE
- Red Hat Enterprise Linux 8 and later
- Open JDK 11
1.3.2. Unsupported on IBM Z and LinuxONE
- Red Hat Enterprise Linux 7
- Open JDK 8, Oracle JDK 8 & 11, IBM JDK 8
1.4. Support for IBM Power architecture
AMQ Streams 2.2 is enabled to run on IBM Power ppc64le architecture.
IBM Power is tested for AMQ Streams running with Kafka and Open JDK 11, on Red Hat Enterprise Linux 8 and later.
1.4.1. Requirements for IBM Power
- Red Hat Enterprise Linux 8 and later
- Open JDK 11
1.4.2. Unsupported on IBM Power
- Red Hat Enterprise Linux 7
- Open JDK 8, Oracle JDK 8 & 11, IBM JDK 8
1.5. KRaft mode (development preview)
Apache Kafka is in the process of phasing out the need for ZooKeeper. You can now try deploying a Kafka cluster in KRaft (Kafka Raft metadata) mode without ZooKeeper.
This feature should be treated as a development preview.
This mode is experimental, intended only for development and testing, and must not be enabled for a production environment.
Currently, the KRaft mode in AMQ Streams has the following major limitations:
- Moving from Kafka clusters with ZooKeeper to KRaft clusters or the other way around is not supported.
- Upgrades and downgrades of Apache Kafka versions are not supported.
- SCRAM-SHA-512 authentication is not supported.
- JBOD storage with multiple disks is not supported.
- Many configuration options are still in development.
1.6. General Availability for Cruise Control
Cruise Control moves from Technology Preview to General Availability (GA). You can install Cruise Control and use it to rebalance your Kafka cluster using optimization goals — defined constraints on CPU, disk, network load, and more. In a balanced Kafka cluster, the workload is more evenly distributed across the broker pods.
Cruise Control helps to reduce the time and effort involved in running an efficient and balanced Kafka cluster.
A zipped distribution of Cruise Control is available for download from the AMQ Streams software downloads page. To install Cruise Control, you configure each Kafka broker to use the provided Metrics Reporter. Then, you set Cruise Control properties, including optimization goals, and start Cruise Control using the provided script.
The Cruise Control server is hosted on a single machine for the whole Kafka cluster.
When Cruise Control is running, you can use the REST API to:
- Generate dry run optimization proposals from multiple optimization goals
- Initiate an optimization proposal to rebalance the Kafka cluster
Other Cruise Control features are not currently supported, including notifications, write-your-own goals, and changing the topic replication factor.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}