Skip to content

Port https://github.com/elastic/cloud/pull/136934 to new docs #664

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
florent-leborgne merged 3 commits into from
Mar 5, 2025
Merged

Port https://github.com/elastic/cloud/pull/136934 to new docs #664

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b395079
Port https://github.com/elastic/cloud/pull/136934 to new docs
florent-leborgne Mar 5, 2025
f7ac960
oupsie oupsie linkie linkie
florent-leborgne Mar 5, 2025
4fb4061
Merge branch 'main' into port-data-tier-change-from-cloud-repo
florent-leborgne Mar 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions manage-data/lifecycle/data-tiers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,12 +111,28 @@ To add a data tier to an existing deployment:

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

:::{important}
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.

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:
* 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.
* 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.
* 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.

Read [https://www.elastic.co/cloud/shared-responsibility](https://www.elastic.co/cloud/shared-responsibility) for additional details.
If in doubt, reach out to Support.
:::

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).

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:

```sh
# cold data tier searchable snapshot indices
GET /_cat/indices/restored-*

# frozen data tier searchable snapshot indices
GET /_cat/indices/partial-*
```

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