Skip to content

Commit 0c0f0eb

Browse files
authored
Merge branch 'main' into fix-logs-formatting
2 parents 24c8959 + 353cbd8 commit 0c0f0eb

16 files changed

+191
-1118
lines changed

manage-data/lifecycle/data-tiers.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,12 +111,28 @@ To add a data tier to an existing deployment:
111111

112112
#### Disable a data tier [disable-a-data-tier]
113113

114+
:::{important}
115+
Disabling a data tier, attempting to scale nodes down in size, reducing availability zones, or reverting an [autoscaling](/deploy-manage/autoscaling.md) change can all result in cluster instability, cluster inaccessibility, and even data corruption or loss in extreme cases.
116+
117+
To avoid this, especially for [production environments](/deploy-manage/production-guidance.md), and in addition to making configuration changes to your indices and ILM as described on this page:
118+
* Review the disk size, CPU, JVM memory pressure, and other [performance metrics](/deploy-manage/monitor/monitoring-data/access-performance-metrics-on-elastic-cloud.md) of your deployment **before** attempting to perform the scaling down action.
119+
* Make sure that you have enough resources and [availability zones](/deploy-manage/production-guidance/availability-and-resilience.md) to handle your workloads after scaling down.
120+
* Check that your [deployment hardware profile](/deploy-manage/deploy/elastic-cloud/ec-change-hardware-profile.md) (for {{ech}}) or [deployment template](/deploy-manage/deploy/cloud-enterprise/configure-deployment-templates.md) (for {{ece}}) is correct for your business use case. For example, if you need to scale due to CPU pressure increases and are using a *Storage Optimized* hardware profile, consider switching to a *CPU Optimized* configuration instead.
121+
122+
Read [https://www.elastic.co/cloud/shared-responsibility](https://www.elastic.co/cloud/shared-responsibility) for additional details.
123+
If in doubt, reach out to Support.
124+
:::
125+
114126
The process of disabling a data tier depends on whether we are dealing with [searchable snapshots](#ece-disable-searchable-snapshot-data-tier) or [regular indices](#ece-disable-non-searchable-snapshot-data-tier).
115127

116128
The hot and warm tiers store regular indices, while the frozen tier stores searchable snapshots. However, the cold tier can store either regular indices or searchable snapshots. To check if a cold tier contains searchable snapshots perform the following request:
117129

118130
```sh
131+
# cold data tier searchable snapshot indices
119132
GET /_cat/indices/restored-*
133+
134+
# frozen data tier searchable snapshot indices
135+
GET /_cat/indices/partial-*
120136
```
121137

122138
##### Non-searchable snapshot data tier [ece-disable-non-searchable-snapshot-data-tier]

raw-migrated-files/docs-content/serverless/security-automated-response-actions.md

Lines changed: 0 additions & 39 deletions
This file was deleted.

raw-migrated-files/docs-content/serverless/security-isolate-host.md

Lines changed: 0 additions & 178 deletions
This file was deleted.

0 commit comments

Comments
 (0)