Important

You are viewing documentation for an older version of Confluent Platform. For the latest, click here.

Migrate to Confluent Platform

Migrating from Confluent Platform using only Confluent Community components

The migration path to Confluent Platform depends on how you originally installed Confluent Open Source download (5.0.x and earlier) or Confluent Community download (5.0.x and later).

Note

The installation package names end with the Scala version that the Kafka is built on. For example, the confluent-platform-2.12 package is for Confluent Platform 5.5.15 and is based on Scala 2.12.

The Zip and Tar packages contain the Confluent Platform version followed by the Scala version. For example, a Zip package, confluent-5.5.15-2.12.zip denotes Confluent Platform version 5.5.15 and Scala version 2.12.

DEB Packages via apt or RPM Packages via yum

The Confluent Platform packages are umbrella packages that contain everything in Confluent Platform using only Confluent Community components plus additional enterprise packages. You can install the additional enterprise packages in your existing community deployment by running:

sudo yum install confluent-platform-2.12

or

sudo apt-get install confluent-platform-2.12

TAR or ZIP archives

If you installed Confluent Platform using only Confluent Community components from TAR or ZIP archives, you must download and install a new Confluent Platform archive that contains the entire platform.

  • Download the Confluent Platform TAR or ZIP archive from https://www.confluent.io/download/.
  • Extract the contents of the archive into a new Confluent Platform install directory. For ZIP files, use a GUI to extract the contents or run this command in a terminal:
unzip confluent-5.5.15-2.12.zip

tar xzf confluent-5.5.15-2.12.tar.gz
  • Copy all configuration files from ./etc, including ./etc/kafka, ./etc/kafka-rest, ./etc/schema-registry, and ./etc/confluent-control-center into the new directory you created in previous step.
  • Stop all Apache Kafka® services running in the Confluent Platform using only Confluent Community components directory. Depending on what was running, this will include kafka-rest, schema-registry, connect-distributed, kafka-server and zookeeper-server.
  • Start the corresponding services in the Confluent Platform directory, and in addition start any new Enterprise services you wish you use - for example confluent-control-center.
  • Repeat these steps on all Confluent servers, one server at a time, to perform rolling migration.
  • If at any time you want to move back to Confluent Platform using only Confluent Community components, simply stop the services in the Confluent Platform installation directory and start them in the Confluent Platform using only Confluent Community components directory.

Migrating from Kafka

Download and install a new Confluent Platform archive that contains the entire platform.

  • Download the Confluent Platform TAR or ZIP archive from https://www.confluent.io/download/.

  • Extract the contents of the archive into a new Confluent Platform install directory. For ZIP files, use a GUI to extract the contents or run this command in a terminal:

    unzip confluent-5.5.15-2.12.zip

    For TAR files run this command:

    tar xzf confluent-5.5.15-2.12.tar.gz

  • Copy all configuration files from ./etc, including ./etc/kafka, ./etc/kafka-rest, ./etc/schema-registry, and ./etc/confluent-control-center into the new directory you created in previous step.

  • Stop all Kafka services running in the Confluent Platform using only Confluent Community components directory. Depending on what was running, this will include kafka-rest, schema-registry, connect-distributed, kafka-server and zookeeper-server.

  • Start the corresponding services in the Confluent Platform directory, and in addition start any new Enterprise services you wish you use, for example confluent-control-center.

  • Repeat these steps on all Confluent servers, one server at a time, to perform rolling migration.

  • If at any time you want to move back to Confluent Platform using only Confluent Community components, simply stop the services in the Confluent Platform installation directory and start them in the Confluent Platform using only Confluent Community components directory.