The following machine recommendations are for installing individual Confluent Platform components:
|Control Center||1||300 GB, preferably SSDs||32 GB RAM (JVM default 6 GB)||8 cores or more|
||64 GB RAM||Dual 12 core sockets|
|Connect||2||Only required for installation||0.5 - 4 GB heap size depending on connectors||Typically not CPU- bound. More cores is better than faster cores.|
|ksqlDB||2||Use SSD. Sizing depends on the number of concurrent queries and the aggregation performed.||20 GB RAM||4 cores|
|REST Proxy||2||Only required for installation||1 GB overhead plus 64 MB per producer and 16 MB per consumer||16 cores to handle HTTP requests in parallel and background threads for consumers and producers.|
|Schema Registry||2||Only required for installation||1 GB heap size||Typically not CPU- bound. More cores is better than faster cores.|
Each write to ZooKeeper must be persisted in the transaction log before the client gets an ack. Using SSD reduces the ZooKeeper write latency.
|4 GB RAM||2-4 Cores|
If you don’t see your region listed, contact Confluent. Additional regions can be supported by request.
- Amazon Web Services (AWS)
- ap-northeast-1 (Tokyo)
- ap-south-1 (Mumbai)
- ap-southeast-1 (Singapore)
- ap-southeast-2 (Sydney)
- ca-central-1 (Canada Central)
- eu-central-1 (Frankfurt)
- eu-west-1 (Ireland)
- eu-west-2 (London)
- eu-west-3 (Paris)
- sa-east-1 (São Paulo)
- us-east-1 (N. Virginia)
- us-east-2 (Ohio)
- us-west-2 (Oregon)
- Azure (Microsoft Azure)
- australiaeast (New South Wales)
- canadacentral (Canada)
- centralus (Iowa)
- eastus (Virginia)
- eastus2 (Virginia)
- francecentral (France)
- northeurope (Ireland)
- southeastasia (Singapore)
- uksouth (London)
- westus2 (Washington)
- westeurope (Netherlands)
- GCP (Google Cloud Platform)
- asia-east1 (Taiwan)
- asia-east2 (Hong Kong)
- asia-northeast1 (Tokyo)
- asia-south1 (Mumbai)
- asia-southeast1 (Singapore)
- asia-southeast-2 (Jakarta)
- australia-southeast1 (Sydney)
- europe-north1 (Finland)
- europe-west1 (Belgium)
- europe-west2 (London)
- europe-west3 (Frankfurt)
- europe-west4 (Netherlands)
- northamerica-northeast1 (Montreal)
- southamerica-east-1 (São Paulo)
- us-central1 (Iowa)
- us-east1 (S. Carolina)
- us-east4 (N. Virginia)
- us-west1 (Oregon)
- us-west2 (Los Angeles)
- us-west4 (Las Vegas)
|RHEL/CentOS 6.x (deprecated)||yes||yes||yes||yes||yes||yes||yes||yes||yes|
|Ubuntu 14.04 LTS (deprecated)||yes||yes||yes||yes||yes||yes||yes||yes||yes|
|Ubuntu 16.04 LTS||yes||yes||yes||yes||yes||yes||yes||yes||yes|
|Ubuntu 18.04 LTS||yes||yes||yes||no||no||no||no||no||no|
- Windows is not currently supported for Confluent Platform. Windows users can download and use the ZIP and TAR archives, but must run the JAR files directly.
- Windows is supported by the C/C++ and .NET clients.
- macOS 10.13 and later is supported for testing and development purposes only.
- For the file descriptor requirement for Kafka, see File Descriptors and mmap.
- Control Center requires many open RocksDB files. Set the ulimit for the number of open files (
ulimit -n) to a minimum value of 16384.
- For the other Confluent Platform components, specifically Schema Registry and Replicator, you can leave the ulimit as the OS default.
Java 8 and Java 11 are supported in this version of Confluent Platform (Java 9 and 10 are not supported). For more information, see Java supported versions. You need to separately install the correct version of Java before you start the Confluent Platform installation process.
Control Center relies heavily on Kafka, so a fast and reliable network is important for performance. Modern datacenter networking speed of 1 GbE, 10 GbE should be sufficient.
By default the Confluent Platform components use these ports to communicate. These ports must be open.
|Kafka brokers (plain text)||9092|
|Kafka inter-broker communication||9091|
|Confluent Control Center||9021|
|Kafka Connect REST API||8083|
|ksqlDB Server REST API||8088|
|Metadata Service (MDS)||8090|
|Schema Registry REST API||8081|
|ZooKeeper||2181, 2888, 3888|
Clock synchronization on each Kafka broker is required to ensure the full system functions
correctly. For example, secure network communication with the brokers that rely on
TLS certificate verification may fail if clocks are not synchronized. Clock synchronization
can be achieved using utilities like
ntpd that implement the Network Time Protocol (NTP).