This page provides the technical capabilities and limitations of the Cloud Analytics with Kafka® MirrorMaker offer.
We continuously improve our offers. You can follow and submit ideas to add to our roadmap.
Capabilities and limitations
Supported regions
To view Cloud Analytics availability, please see our regions and availability webpage.
Entire analytics instances have to be in the same region.
Kafka® MirrorMaker versions
The Cloud Analytics offer supports the following Kafka® versions:
- Kafka® MirrorMaker 3.8
You can follow Kafka® Release Cycle on their official page.
Kafka® clients
You can use any of the Kafka®-recommended clients to access your cluster.
Additionally, Kafka® Connect is available at OVHcloud.
Plans
The available plans are:
- Essential: 1 node
- Business: 3 nodes
- Enterprise: 6 nodes
Your choice of plan affects the number of nodes your cluster can run as well as the SLA.
License type
Kafka® software is under the Apache 2 license, a liberal open-source license. More information can be found here.
Hardware resources
For more information about node types and their specifications, see our pricing page.
Features
Network
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 are unmetered.
The analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
Private network considerations
Here are some considerations to take into account when using a private network:
- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g., you won’t be able to delete the network if you didn’t stop the Cloud Analytics services first.
- When connecting from an outside subnet, the OpenStack IP gateway must be enabled in the subnet used for the Analytics service. The customer is responsible for any other custom network setup.
- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
- OpenStack subnet routes announcement will not be applied to your services.
- You can only create private network services if you are the original owner of the network. You cannot create private network services on a shared network.
Authorized IPs
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorize incoming traffic. Until then, your service will be unreachable.
Kafka® replication and data retention
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 two Kafka® clusters to create replication flows.
Replication flows allowed parameters are:
- Source
- Target
- Topics
- Topics exclusion
- Sync group offset
- Sync interval in seconds (s)
- Heartbeats (true/false)
Data retention is only limited by your cluster storage space.
Advanced parameters
Though advanced parameters are supported for Kafka®, they are not supported for Kafka® MirrorMaker.
Backups
Kafka® is a streaming tool. We don't back up Kafka® data.
Logs and metrics
Logs and metrics are available through the Control Panel and the API. Additionally, cross-service integration can be configured to leverage your logs and metrics in other Cloud Databases and Analytics services. You could then view your Kafka® MirrorMaker logs in OpenSearch™ and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL®). See our Set up a service Integration guide for more information.
- Logs retention: 1000 lines of logs
- Metrics retention: 1 calendar month
Please note that if the analytics instance is deleted, logs and metrics are also automatically deleted.
Users and roles
The creation of users is allowed via the Control Panel and API.
You can specify a username for each user. By default, the role is admin.
Data encryption
For detailed information about encryption, see our Security Overview guide.
Go further
For more information and tutorials, please see our other Managed Databases & Analytics or Platform as a Service guides. You can also explore the guides for other OVHcloud products and services.
OVHcloud Managed Databases and Analytics:
- Grafana® is a registered trademark of Grafana Labs and is used with the permission of Grafana Labs. OVH SAS and its subsidiaries are not affiliated with or endorsed by Grafana Labs.
- Kafka® is a registered trademark of The Apache Software Foundation and has been licensed for use by OVHcloud, who has no affiliation with and is not endorsed by The Apache Software Foundation.
- MongoDB® is a registered trademark of MongoDB, Inc.
- MySQL® is a registered trademark of Oracle and/or its affiliates.
- PostgreSQL® is a registered trademark of the PostgreSQL Community Association of Canada.