Cloudera Distribution of Apache Kafka Requirements and Supported Versions
The following sections describe software requirements and supported versions of complementary software for Cloudera Distribution of Apache Kafka:
Supported CDH and Cloudera Manager Releases
For the list of supported releases of CDH and Cloudera Manager, see CDH and Cloudera Manager Supported Versions.
Supported Integrations
- Flume and Spark connectors to Kafka are included with CDH 5.7.x and higher and only work with Kafka 2.0.x and higher.
- Sentry authorization integration with Kafka only works with Kafka 2.1.x and higher on CDH 5.9.x and higher.
Supported Operating Systems
For the list of supported operating systems, see CDH and Cloudera Manager Supported Operating Systems.
SUSE Linux Enterprise Server (SLES)
Unlike CentOS, SLES limits virtual memory by default. Changing this default requires adding the following entries to the /etc/security/limits.conf file:
* hard as unlimited * soft as unlimited
Supported JDK Versions
For a listed of supported and tested JDK versions for Kafka 2.2.x and below, see CDH and Cloudera Manager Supported JDK Versions.
Ports Used by Kafka
Kafka uses the TCP ports listed in the following table. Before deploying Kafka, ensure that these ports are open on each system.
Component | Service | Port | Access Requirement | Comment |
---|---|---|---|---|
Broker |
TCP Port |
9092 |
External/Internal |
The primary communication port used by producers and consumers; also used for inter-broker communication. |
Broker |
TLS/SSL Port |
9093 |
External/Internal |
A secured communication port used by producers and consumers; also used for inter-broker communication. |
Broker |
JMX Port |
9393 |
Internal |
Internal use only. Used for administration via JMX. |
MirrorMaker |
JMX Port |
9394 |
Internal |
Internal use only. Used to administer the producer and consumer of the MirrorMaker. |
Broker |
HTTP Metric Report Port |
24042 |
Internal |
Internal use only. This is the port via which the HTTP metric reporter listens. It is used to retrieve metrics through HTTP instead of JMX. |