DC/OS Confluent ZooKeeper is an automated service that makes it easy to deploy and manage Confluent ZooKeeper on DC/OS for the purposes of running the DC/OS Apache Kafka and DC/OS Confluent Kafka Services. ZooKeeper is a centralized service for maintaining configuration and naming information, as well as providing distributed synchronization and group services.
- Single command installation for rapid provisioning.
- CLI for easy management.
- Cluster size of 3 or 5 nodes for fault tolerance in production.
- Multiple ZooKeeper clusters sharing a single DC/OS cluster for multi-tenancy.
- Rolling software and configuration updates for runtime maintenance.
Release notes for version 2.8.0-5.5.1…Read More
To start a basic test cluster with three servers, run the following command on the DC/OS CLI.…Read More
This section describes some advanced features of the DC/OS Confluent ZooKeeper service.…Read More
The default DC/OS Confluent ZooKeeper installation provides reasonable defaults for trying out the service, but may not be sufficient for production use. You may require a different configuration depending on the context of the deployment.…Read More
The DC/OS Confluent ZooKeeper service provides a robust API (accessible by HTTP or DC/OS CLI) for managing, repairing, and monitoring the service. Here, only the CLI version is presented for conciseness, but see the API Reference for HTTP instructions.…Read More
Enterprise DC/OS 1.10 introduced a convenient command line option that allows for easier updates to a service’s configuration and version, as well as allowing users to inspect the status of an update, to pause and resume updates, and to restart or complete steps if necessary.…Read More
The DC/OS Confluent ZooKeeper service allows you to create a service account to configure access for Confluent ZooKeeper. The service allows you to create and assign permissions as required for access.…Read More
If you are using DC/OS 1.10 or later and the installed service has a version later than 2.0.0-x, then uninstalling the service is simple.…Read More
After a configuration change, the service may enter an unhealthy state. This commonly occurs when an invalid configuration change was made by the user. Certain configuration values may not be changed, or may not be decreased. To verify whether this is the case, check the service’s deploy plan for any errors.…Read More
The DC/OS Confluent ZooKeeper Service implements a REST API that may be accessed from outside the cluster. The
Only 3 or 5 ZooKeeper nodes are allowed. The value may not be changed after deployment.…Read More
DC/OS and certified package version support policy are described in detail here.…Read More