M3db - Capabilities and Limitations
Discover the capabilities and limitations of Public Cloud Databases for M3db
Last updated January 19th, 2023
Objective
This page provides the technical capabilities and limitations of the Public Cloud Databases m3db 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.
Capabilities and limitations
Supported regions and multi-AZ
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)
Entire database instances have to be in the same region. Multi-AZ is currently not supported.
M3db versions
The Public Cloud Databases offer supports the following m3db versions:
- m3db 1.1
m3db recommends always installing and using the latest stable version.
Plans
Three plans are available:
- Essential
- Business
- Enterprise
Here is an overview of the various plans' capabilities:
| Plan | Number of nodes by default | Read replicas |
|---|---|---|
| Essential | 1 | No |
| Business | 3 | Planned |
| Enterprise | 6 | Planned |
Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
Nodes and replicas
- Essential: The cluster can support at most one node.
- Business: The cluster is delivered with 2 nodes by default. Adding read replicas is planned.
- Enterprise: The cluster is delivered with 3 nodes by default. Adding read replicas is planned.
License type
Each cluster is provided with the M3db Community (GPL) license.
If any, license cost is included inside the service plans. You can't bring your own licenses.
Hardware resources
Here are the node types you can choose from:
Essentials plans
| Name | Disk (GB) | Cores | Memory (GB) |
|---|---|---|---|
| db1-7 | 160 | 2 | 7 |
| db1-15 | 320 | 4 | 15 |
| db1-30 | 640 | 8 | 30 |
| db1-60 | 1280 | 16 | 60 |
Business plans
| Name | Disk (GB) | Cores | Memory (GB) |
|---|---|---|---|
| db1-7 | 480 | 2 | 7 |
| db1-15 | 960 | 4 | 15 |
| db1-30 | 1920 | 8 | 30 |
| db1-60 | 3840 | 16 | 60 |
| db1-120 | 7680 | 32 | 120 |
Enterprise plans
| Name | Disk (GB) | Cores | Memory (GB) |
|---|---|---|---|
| db1-15 | 1920 | 4 | 15 |
| db1-30 | 3840 | 8 | 30 |
| db1-60 | 7680 | 16 | 60 |
| db1-120 | 15360 | 32 | 120 |
Right now, all nodes of a given cluster should be of the same type and live in the same region.
Disk type
The type of storage available may vary according to the region your cluster lives in: see Availability of Public Cloud products for more information about block storage type availability depending on region. Thus, your cluster may be backed by e.g. High Speed or High Speed Gen2 block storage.
Also, the performance caracteristics of the various storage offerings may vary depending on e.g. the storage size your cluster uses: High Speed may offer better iops than High Speed Gen2 for some disk sizes. See Block Storage documentation for more information about those performance caracteristics.
Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
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 unmetered.
Private network considerations
Here are some considerations to take into account when using 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 Public Cloud Databases services first.
- When connecting from outside subnet, Openstack IP gateway must be enabled in the subnet use for the Database service. The customer is responsible for any other custom network setup.
Logs and metrics
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.
- Logs retention: 1000 lines of logs
- Metrics retention: 1 calendar month
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
We want your feedback!
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!
Haben Ihnen die Anleitungen geholfen?
Bevor Sie Ihre Meinung abgeben, nehmen wir gerne Ihre Vorschläge auf, wie wir diese Dokumente verbessern können.
Woran liegt es? An den Bildern, dem Inhalt oder Aufbau der Anleitungen? Schreiben Sie es uns gerne, dann machen wir es zusammen besser.
Ihre Support-Anfragen werden in diesem Formular nicht entgegengenommen. Verwenden Sie hierfür bitte das Formular "Ein Ticket erstellen" .
Vielen Dank. Ihr Feedback wurde gesendet.