[REQUEST]: Update frozen tier support wording for DE

[yctercero]

Description

What: It was pointed out to us here that frozen can have replicas, allowing for high availability. Per the user facing ES docs that are linked below:

By default, searchable snapshot indices are mounted without replicas. Using this will result in a searchable snapshot index being mounted with a single replica for the time period specified, after which the replica will be removed. This option is only permitted on the first searchable snapshot action of a policy.

As a result, we should update our text from:

• Replicas for mission-critical data: Your data should have replicas if it must be highly available. Since frozen tiers don't support replicas, shard unavailability can cause partial rule run failures if rules query frozen tiers. Shard unavailability may also occur during or after {stack} upgrades. If this happens, you can <<manually-run-rules,manually rerun>> rules over the affected time period once the shards are available.

to update for the fact that replicas are available:

• Replicas for mission-critical data: Your data should have replicas if it must be highly available. Since frozen tiers don't support replicas, shard Since frozen tiers don't have replicas by default, shard unavailability can cause partial rule run failures if rules query frozen tiers without replicas. Shard unavailability may also occur during or after {stack} upgrades. If this happens, you can <<manually-run-rules,manually rerun>> rules over the affected time period once the shards are available.

When: Looks like this was merged in this past December so should be in for 8.18+

Resources

This feature was merged December 2024 - PR
This feature for frozen tier is documented - user docs.

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

What release is this request related to?

8.18+

Collaboration model

The documentation team

Point of contact.

Main contact: @yctercero

Stakeholders: @approksiu @MikePaquette

[yctercero]

Updated description to add @marshallmain 's suggestion of mentioning that shard replication is not on by default for frozen:

• Replicas for mission-critical data: Your data should have replicas if it must be highly available. Since frozen tiers don't have replicas by default, shard unavailability can cause partial rule run failures if rules query frozen tiers without replicas. Shard unavailability may also occur during or after {stack} upgrades. If this happens, you can <<manually-run-rules,manually rerun>> rules over the affected time period once the shards are available.