Kafka MirrorMaker - Capabilities and Limitations
Discover the capabilities and limitations of Public Cloud Databases for Kafka MirrorMaker
Discover the capabilities and limitations of Public Cloud Databases for Kafka MirrorMaker
Last updated January 19th, 2023
This page provides the technical capabilities and limitations of the Public Cloud Databases for Kafka MirrorMaker offer.
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at https://github.com/ovh/public-cloud-roadmap/projects/2.
The Public Cloud Databases offer is available in the following regions:
BHS
(Beauharnois, Canada)DE
(Frankfurt, Germany)GRA
(Gravelines, France)SBG
(Strasbourg, France)UK
(London, United Kingdom)WAW
(Warsaw, Poland)Kafka MirrorMaker nodes have to be in the same region. Multi-AZ is currently not supported.
The Public Cloud Databases offer supports the following Kafka versions:
You can follow Kafka Release Cycle on their official page : https://kafka.apache.org/downloads
You can use any of the Kafka-recommended clients to access your cluster.
Please note that Kafka Connect is not available so far.
Three plans are available:
Here is an overview of the various plans' capabilities:
Plan | Number of nodes by default | Additional nodes |
---|---|---|
Essential | 1 | No |
Business | 3 | No |
Enterprise | 6 | No |
Your choice of plan affects the number of nodes your cluster can run as well as the SLA.
Kafka software is under the Apache 2 license, a liberal open-source license. More information on https://github.com/apache/kafka/blob/trunk/LICENSE.
Here are the node types you can choose from:
Essential plans
Name | Disk (GB) | Cores | Memory (GB) |
---|---|---|---|
db1-7 | N/A | 2 | 7 |
db1-15 | N/A | 4 | 15 |
db1-30 | N/A | 8 | 30 |
Business plans
Name | Disk (GB) | Cores | Memory (GB) |
---|---|---|---|
db1-7 | N/A | 2 | 7 |
db1-15 | N/A | 4 | 15 |
db1-30 | N/A | 8 | 30 |
Enterprise plans
Name | Disk (GB) | Cores | Memory (GB) |
---|---|---|---|
db1-7 | N/A | 2 | 7 |
db1-15 | N/A | 4 | 15 |
db1-30 | N/A | 8 | 30 |
Right now, all nodes of a given cluster should be of the same type and distributed in the same region.
Public as well as private networking (vRack) can be used for all the offers.
Ingress and Egress traffic are included in the service plans and unmetered.
Here are some considerations to take into account when using private network:
You can select a Kafka source cluster and a Kafka destination cluster from the same Public Cloud project. External Kafka clusters are not supported so far.
You need at least 2 Kafka clusters to create replication flows.
Replication flows allowed parameters are:
Data retention is only limited by your cluster storage space.
We do not currently support Kafka advanced parameters.
Kafka is a streaming tool. We don't backup Kafka data.
Logs and metrics are available via the OVHcloud Public Cloud Control Panel. As of today, you can't export logs and metrics, nor plug them into a remote tool.
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
We would love to help answer questions and appreciate any feedback you may have.
Are you on Discord? Connect to our channel at https://discord.gg/ovhcloud and interact directly with the team that builds our databases service!
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community