In ADCM a service means a software that performs some function. Examples of services for ADS clusters: NiFi, Kafka, ZooKeeper, etc. The steps for adding services to a cluster are listed below:
From the CLUSTERS tab switch to the cluster configuring. To do this, click the row that contains the added cluster or click the icon in the Config column. Both methods open the cluster menu.Switching to cluster configuring
Open the Services tab in the cluster menu and click Add services.Switching to services adding
In the opened dialog, select the services that should be added to the cluster, and click Add.Choosing services
When adding ksqlDB, Schema-Registry, Kafka REST Proxy services, you should sign a Confluent license agreement. To do this, you need to read the text of the agreement and accept it by clicking Yes.
The brief description of available services is listed below.
Services that can be added to the ADS cluster Service Purpose
The centralized coordination service for distributed applications is used to store metadata about the sections (partitions) of topics and Apache Kafka brokers, as well as to select a broker as a Kafka controller. Informs each Kafka broker about the current state of the cluster
An open-source distributed event streaming platform used for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications
Apache Kafka management tool
Kafka REST Proxy
Service provides a RESTful interface to an Apache Kafka cluster, making it easy to produce and consume messages, view the state of the cluster, and perform administrative actions without using the native Kafka protocol or clients
The service performs the following functions:
Storing a version history of all Avro schemas based on a specified subject naming policy with support for several compatibility options.
The ability to change Avro schemas according to configured compatibility settings and extended support for these schema types.
Providing a RESTful interface for storing and retrieving Avro schemas.
Providing serializers that connect to Apache Kafka clients handling message map storage and retrieval.
Аn open-source SQL streaming engine that provides real-time data processing using Apache Kafka
A simple event (message) processing platform that provides real-time control of data flows from various sources using a graphical interface
A subproject of Apache NiFi — is a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at the source of its creation
Agents sending information about hosts and services in monitoring. The service should be added after the monitoring cluster is installed and configured, if monitoring of the current cluster is planned
A tool for scalably and reliably streaming data between Kafka and other data systems
The minimal set of services recommended for ADS clusters is described below:
These services make up the core of Streaming and are sufficient for fast and easy installation and management of Arenadata Streaming with Arenadata Cluster Manager. The full list of services depends on the requirements of a particular project. Not all services are required to be installed. For example, if you do not plan to use NiFi, then there is no need to add that service. Also, if a monitoring service is used (not based on Graphite), there is no need to install agents from Monitoring Clients. However, if you plan to use Kafka, the Kafka and ZooKeeper services are required. The same can be said about the NiFi service. In this case, the service can consist of mandatory and optional components. For example, a ksqlDB service consists of a required Server component and an optional Client component.
As a result, the added services are displayed at the Services tab.The result of successful adding services to a cluster
NOTEYou can also add services later. The process of adding new services to already running cluster does not differ from installing a service from scratch.