You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -36,9 +36,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
36
36
37
37
The Public Cloud Databases offer supports the following OpenSearch versions:
38
38
39
-
- OpenSearch 1.1
39
+
- OpenSearch 1
40
+
- OpenSearch 2
40
41
41
-
You can follow version history for OpenSearch version on their official page: <https://opensearch.org/docs/latest/version-history/>
42
+
Please refer to the [DBMS lifecycle policy guide](https://docs.ovh.com/gb/en/publiccloud/databases/lifecycle-policy/) for recommendations on version upgrades and end of life announcements of major versions. You can, additionally, follow version history for OpenSearch version on their official page: <https://opensearch.org/docs/latest/version-history/>
42
43
43
44
### OpenSearch clients and plugins compatibility
44
45
@@ -60,13 +61,16 @@ Here is an overview of the various plans' capabilities:
60
61
|*Business*| 3 | Planned |
61
62
|*Enterprise*| 6 | Planned |
62
63
63
-
Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as backup retention.
64
+
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.
65
+
66
+
> [!primary]
67
+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
64
68
65
69
#### Nodes and replicas
66
70
67
71
-**Essential**: the cluster can support at most one node.
68
-
-**Business**: The cluster is delivered with 3 nodes by default.
69
-
-**Enterprise**: The cluster is delivered with 6 nodes by default.
72
+
-**Business**: the cluster is delivered with 3 nodes by default.
73
+
-**Enterprise**: the cluster is delivered with 6 nodes by default.
70
74
71
75
#### License type
72
76
@@ -79,35 +83,44 @@ Here are the node types you can choose from:
Right now, all nodes of a given cluster should be of the same type and distributed in the same region.
110
115
116
+
#### Flexible storage
117
+
118
+
You can increased the storage of your cluster up to the maximum allowed for a given reference. Please refer to the [Resize your cluster storage guide](https://docs.ovh.com/gb/en/publiccloud/databases/resize-cluster-storage/) for more information.
119
+
120
+
#### Node template upgrade
121
+
122
+
You can upgrade the node template of your cluster to scale your hardware resources up. This operation causes no interruption of service but be aware that you will not be able to downgrade the node template afterwards.
123
+
111
124
#### Disk type
112
125
113
126
The type of storage available may vary according to the region your cluster lives in: see [Availability of Public Cloud products](https://www.ovhcloud.com/de/public-cloud/regions-availability/) 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.
@@ -120,6 +133,14 @@ Public Cloud Databases will select the most efficient disk type for your cluster
120
133
121
134
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
122
135
136
+
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
137
+
138
+
1. When reaching a concerning level of disk usage, a warning email is sent.
139
+
2. When reaching a concerning level of disk usage, the service is moved in the "DISK_FULL" state, and "read-only" mode, meaning no more writes can be done.
140
+
3. You then have the ability to upgrade to a higher service plan with more storage.
141
+
142
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/gb/en/publiccloud/databases/handling-disk-full/) for more information.
143
+
123
144
### Features
124
145
125
146
#### Plugin enabled by default
@@ -157,10 +178,13 @@ Here are some considerations to take into account when using private network:
157
178
- 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.
158
179
159
180
181
+
##### Authorised IPs
182
+
183
+
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic, until then your service will be unreachable.
160
184
161
185
#### Advanced parameters
162
186
163
-
We do not currently support OpenSearch advanced parameters.
187
+
You can customize your Opensearch further through the use of advanced parameters. See the [Advanced parameters references documentation](https://help.ovhcloud.com/csm/en-gb-public-cloud-databases-opensearch-advanced-parameters-references?id=kb_article_view&sysparm_article=KB0054697) for more information about which ones are supported.
164
188
165
189
#### Backups
166
190
@@ -172,8 +196,7 @@ We do not currently support OpenSearch advanced parameters.
172
196
173
197
#### Logs and metrics
174
198
175
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
176
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
199
+
Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration could be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Opensearch metrics in Grafana. See the [Cross Service Integration documentation](https://docs.ovh.com/gb/en/publiccloud/databases/cross-service-integration/) for more information.
Copy file name to clipboardExpand all lines: pages/platform/databases/opensearch_01_capabilities/guide.en-asia.md
+51-28Lines changed: 51 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ slug: opensearch/capabilities
4
4
excerpt: Discover the capabilities and limitations of Public Cloud Databases for OpenSearch
5
5
section: OpenSearch - Guides
6
6
order: 010
7
-
updated: 2023-01-19
7
+
updated: 2023-04-22
8
8
---
9
9
10
-
**Last updated January 19th, 2023**
10
+
**Last updated April 22nd, 2023**
11
11
12
12
## Objective
13
13
@@ -34,9 +34,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
34
34
35
35
The Public Cloud Databases offer supports the following OpenSearch versions:
36
36
37
-
- OpenSearch 1.1
37
+
- OpenSearch 1
38
+
- OpenSearch 2
38
39
39
-
You can follow version history for OpenSearch version on their official page: <https://opensearch.org/docs/latest/version-history/>
40
+
Please refer to the [DBMS lifecycle policy guide](https://docs.ovh.com/gb/en/publiccloud/databases/lifecycle-policy/) for recommendations on version upgrades and end of life announcements of major versions. You can, additionally, follow version history for OpenSearch version on their official page: <https://opensearch.org/docs/latest/version-history/>
40
41
41
42
### OpenSearch clients and plugins compatibility
42
43
@@ -58,13 +59,16 @@ Here is an overview of the various plans' capabilities:
58
59
|*Business*| 3 | Planned |
59
60
|*Enterprise*| 6 | Planned |
60
61
61
-
Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as backup retention.
62
+
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.
63
+
64
+
> [!primary]
65
+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
62
66
63
67
#### Nodes and replicas
64
68
65
69
-**Essential**: the cluster can support at most one node.
66
-
-**Business**: The cluster is delivered with 3 nodes by default.
67
-
-**Enterprise**: The cluster is delivered with 6 nodes by default.
70
+
-**Business**: the cluster is delivered with 3 nodes by default.
71
+
-**Enterprise**: the cluster is delivered with 6 nodes by default.
68
72
69
73
#### License type
70
74
@@ -77,35 +81,44 @@ Here are the node types you can choose from:
Right now, all nodes of a given cluster should be of the same type and distributed in the same region.
108
113
114
+
#### Flexible storage
115
+
116
+
You can increased the storage of your cluster up to the maximum allowed for a given reference. Please refer to the [Resize your cluster storage guide](https://docs.ovh.com/gb/en/publiccloud/databases/resize-cluster-storage/) for more information.
117
+
118
+
#### Node template upgrade
119
+
120
+
You can upgrade the node template of your cluster to scale your hardware resources up. This operation causes no interruption of service but be aware that you will not be able to downgrade the node template afterwards.
121
+
109
122
#### Disk type
110
123
111
124
The type of storage available may vary according to the region your cluster lives in: see [Availability of Public Cloud products](https://www.ovhcloud.com/asia/public-cloud/regions-availability/) 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.
@@ -118,6 +131,14 @@ Public Cloud Databases will select the most efficient disk type for your cluster
118
131
119
132
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
120
133
134
+
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
135
+
136
+
1. When reaching a concerning level of disk usage, a warning email is sent.
137
+
2. When reaching a concerning level of disk usage, the service is moved in the "DISK_FULL" state, and "read-only" mode, meaning no more writes can be done.
138
+
3. You then have the ability to upgrade to a higher service plan with more storage.
139
+
140
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/gb/en/publiccloud/databases/handling-disk-full/) for more information.
141
+
121
142
### Features
122
143
123
144
#### Plugin enabled by default
@@ -154,10 +175,13 @@ Here are some considerations to take into account when using private network:
154
175
- 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.
155
176
- 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.
156
177
178
+
##### Authorised IPs
179
+
180
+
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic, until then your service will be unreachable.
157
181
158
182
#### Advanced parameters
159
183
160
-
We do not currently support OpenSearch advanced parameters.
184
+
You can customize your Opensearch further through the use of advanced parameters. See the [Advanced parameters references documentation](https://help.ovhcloud.com/csm/en-gb-public-cloud-databases-opensearch-advanced-parameters-references?id=kb_article_view&sysparm_article=KB0054697) for more information about which ones are supported.
161
185
162
186
#### Backups
163
187
@@ -169,8 +193,7 @@ We do not currently support OpenSearch advanced parameters.
169
193
170
194
#### Logs and metrics
171
195
172
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
173
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
196
+
Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration could be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Opensearch metrics in Grafana. See the [Cross Service Integration documentation](https://docs.ovh.com/gb/en/publiccloud/databases/cross-service-integration/) for more information.
0 commit comments