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
Copy file name to clipboardExpand all lines: deploy-manage/autoscaling/autoscaling-deciders.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,7 +122,7 @@ The [autoscaling](../../deploy-manage/autoscaling.md) {{ml}} decider (`ml`) calc
122
122
The {{ml}} decider is enabled for policies governing `ml` nodes.
123
123
124
124
::::{note}
125
-
For {{ml}} jobs to open when the cluster is not appropriately scaled, set `xpack.ml.max_lazy_ml_nodes` to the largest number of possible {{ml}} nodes (refer to [Advanced machine learning settings](elasticsearch://reference/elasticsearch/configuration-reference/machine-learning-settings.md#advanced-ml-settings) for more information). In {{ess}}, this is automatically set.
125
+
For {{ml}} jobs to open when the cluster is not appropriately scaled, set `xpack.ml.max_lazy_ml_nodes` to the largest number of possible {{ml}} nodes (refer to [Advanced machine learning settings](elasticsearch://reference/elasticsearch/configuration-reference/machine-learning-settings.md#advanced-ml-settings) for more information). In {{ech}}, this is automatically set.
@@ -38,9 +38,8 @@ For more information, refer to [](/deploy-manage/cloud-organization.md).
38
38
You can have multiple hosted deployments and serverless projects in the same {{ecloud}} organization, and each deployment type has its own specificities.
39
39
40
40
41
-
||||
42
-
| --- | --- | --- |
43
41
| Option | Serverless | Hosted |
42
+
| --- | --- | --- |
44
43
|**Cluster management**| Fully managed by Elastic. | You provision and manage your hosted clusters. Shared responsibility with Elastic. |
45
44
|**Scaling**| Autoscales out of the box. | Manual scaling or autoscaling available for you to enable. |
46
45
|**Upgrades**| Automatically performed by Elastic. | You choose when to upgrade. |
Copy file name to clipboardExpand all lines: deploy-manage/deploy/elastic-cloud/azure-marketplace-pricing.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,8 @@ The pricing plan update enables us to align with market trends and adapt to chan
23
23
24
24
These pricing changes will apply to customers who are currently paying for Azure Marketplace services in non-USD currencies. If you are paying in USD, your pricing and billing will remain unchanged.
25
25
26
-
||||
27
-
| --- | --- | --- |
28
26
| Currency | Price | Elastic Billing Units for Azure† |
Copy file name to clipboardExpand all lines: deploy-manage/monitor/cloud-health-perf.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ You can also search and filter the table based on affected resources, such as in
45
45
:alt: {{es}} Health page with details and troubleshooting
46
46
:::
47
47
48
-
For each issue you can either use a troubleshooting link or get a suggestion to contact support, in case you need help. The [troubleshooting documentation](/troubleshoot/elasticsearch/elasticsearch.md) for {{es}} provides more details on specific errors.
48
+
For more information about specific errors, refer to [](/troubleshoot/elasticsearch.md). You can also [contact us](/troubleshoot/index.md#contact-us) if you need more help.
49
49
50
50
### Health warnings [ec-es-health-warnings]
51
51
@@ -74,7 +74,7 @@ deployment:
74
74
ess:
75
75
```
76
76
77
-
{{ess}} deployments offer an additional **Performance** page to get further information about your cluster performance.
77
+
{{ech}} deployments offer an additional **Performance** page to get further information about your cluster performance.
78
78
79
79
If you observe issues on search and ingest operations in terms of increased latency or throughput for queries, these might not be directly reported on the **Health** page, unless they are related to shard health or master node availability.
80
80
@@ -131,23 +131,23 @@ If you need your cluster to be able to sustain a certain level of performance, y
131
131
132
132
We’ve compiled some guidelines to help you ensure the health of your deployments over time. These can help you to better understand the available performance metrics, and to make decisions involving performance and high availability.
133
133
134
-
[Why is my node(s) unavailable?](/troubleshoot/monitoring/unavailable-nodes.md)
134
+
[](/troubleshoot/monitoring/unavailable-nodes.md)
135
135
: Learn about common symptoms and possible actions that you can take to resolve issues when one or more nodes become unhealthy or unavailable.
136
136
137
-
[Why are my shards unavailable?](/troubleshoot/monitoring/unavailable-shards.md)
: Provide instructions on how to troubleshoot issues related to unassigned shards.
139
139
140
-
[Why is performance degrading over time?](/troubleshoot/monitoring/performance.md)
140
+
[](/troubleshoot/monitoring/performance.md)
141
141
: Address performance degradation on a smaller size Elasticsearch cluster.
142
142
143
-
[Is my cluster really highly available?](/troubleshoot/monitoring/high-availability.md)
143
+
[](/troubleshoot/monitoring/high-availability.md)
144
144
: High availability involves more than setting multiple availability zones (although that’s really important!). Learn how to assess performance and workloads to determine if your deployment has adequate resources to mitigate a potential node failure.
145
145
146
-
[How does high memory pressure affect performance?](/troubleshoot/monitoring/high-memory-pressure.md)
: Learn about typical memory usage patterns, how to assess when the deployment memory usage levels are problematic, how this impacts performance, and how to resolve memory-related issues.
148
148
149
-
[Why are my cluster response times suddenly so much worse?](/troubleshoot/monitoring/cluster-response-time.md)
Copy file name to clipboardExpand all lines: deploy-manage/production-guidance/optimize-performance/size-shards.md
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,33 @@ mapped_pages:
5
5
6
6
# Size your shards [size-your-shards]
7
7
8
-
Each index in {{es}} is divided into one or more shards, each of which may be replicated across multiple nodes to protect against hardware failures. If you are using [Data streams](../../../manage-data/data-store/data-streams.md) then each data stream is backed by a sequence of indices. There is a limit to the amount of data you can store on a single node so you can increase the capacity of your cluster by adding nodes and increasing the number of indices and shards to match. However, each index and shard has some overhead and if you divide your data across too many shards then the overhead can become overwhelming. A cluster with too many indices or shards is said to suffer from *oversharding*. An oversharded cluster will be less efficient at responding to searches and in extreme cases it may even become unstable.
8
+
## What is a shard? [what-is-a-shard]
9
9
10
+
A shard is a basic unit of storage in {{es}}. Every index is divided into one or more shards to help distribute data and workload across nodes in a cluster. This division allows {{es}} to handle large datasets and perform operations like searches and indexing efficiently. For more detailed information on shards, see [this page](/deploy-manage/distributed-architecture/clusters-nodes-shards.md).
11
+
12
+
## General guidelines [sizing-shard-guidelines]
13
+
14
+
Balancing the number and size of your shards is important for the performance and stability of an {{es}} cluster:
15
+
16
+
* Too many shards can degrade search performance and make the cluster unstable. This is referred to as _oversharding_.
17
+
* Very large shards can slow down search operations and prolong recovery times after failures.
18
+
19
+
To avoid either of these states, implement the following guidelines:
20
+
21
+
### General sizing guidelines
22
+
23
+
* Aim for shard sizes between 10GB and 50GB
24
+
* Keep the number of documents on each shard below 200 million
25
+
26
+
### Shard distribution guidelines
27
+
28
+
To ensure that each node is working optimally, distribute shards evenly across nodes. Uneven distribution can cause some nodes to work harder than others, leading to performance degradation and instability.
29
+
30
+
While {{es}} automatically balances shards, you need to configure indices with an appropriate number of shards and replicas to allow for even distribution across nodes.
31
+
32
+
If you are using [data streams](/manage-data/data-store/data-streams.md), each data stream is backed by a sequence of indices, each index potentially having multiple shards.
33
+
34
+
Despite these general guidelines, it is good to develop a tailored [sharding strategy](#create-a-sharding-strategy) that considers your specific infrastructure, use case, and performance expectations.
10
35
11
36
## Create a sharding strategy [create-a-sharding-strategy]
|[*Hot/Frozen - High Availability*](/deploy-manage/reference-architectures/hotfrozen-high-availability.md)<br>A high availability architecture that is cost optimized for large time-series datasets. | * Have a requirement for cost effective long term data storage (many months or years).<br>* Provide insights and alerts using logs, metrics, traces, or various event types to ensure optimal performance and quick issue resolution for applications.<br>* Apply Machine Learning and Search AI to assist in dealing with the large amount of data.<br>* Deploy an architecture model that allows for maximum flexibility between storage cost and performance.<br> |
32
31
| Additional architectures are on the way.<br>Stay tuned for updates. ||
0 commit comments