Zone Aware Replication
Cortex supports data replication for different services. By default, data is transparently replicated across the whole pool of service instances, regardless of whether these instances are all running within the same availability zone (or data center, or rack) or in different ones.
It is completely possible that all the replicas for the given data are held within the same availability zone, even if the Cortex cluster spans multiple zones. Storing multiple replicas for a given data within the same availability zone poses a risk for data loss if there is an outage affecting various nodes within a zone or a full zone outage.
For this reason, Cortex optionally supports zone-aware replication. When zone-aware replication is enabled, replicas for the given data are guaranteed to span across different availability zones. This requires Cortex cluster to run at least in a number of zones equal to the configured replication factor.
Reads from a zone-aware replication enabled Cortex Cluster can withstand zone failures as long as there are no more than
floor(replication factor / 2) zones with failing instances.
The Cortex services supporting zone-aware replication are:
Distributors / Ingesters: time-series replication
The Cortex time-series replication is used to hold multiple (typically 3) replicas of each time series in the ingesters.
To enable the zone-aware replication for the ingesters you should:
- Configure the availability zone for each ingester via the
-ingester.availability-zoneCLI flag (or its respective YAML config option)
- Rollout ingesters to apply the configured zone
- Enable time-series zone-aware replication via the
-distributor.zone-awareness-enabledCLI flag (or its respective YAML config option). Please be aware this configuration option should be set to distributors, queriers and rulers.
-distributor.shard-by-all-labels setting has an impact on read availability. When enabled, a metric is sharded across all ingesters and querier needs to fetch series from all ingesters while, when disabled, a metric is sharded only across
<replication factor> ingesters.
In the event of a large outage impacting ingesters in more than 1 zone, when
-distributor.shard-by-all-labels=true all queries will fail, while when disabled some queries may still succeed if the ingesters holding the required metric are not impacted by the outage. To learn more about this flag, please refer to distributor arguments.
Store-gateways: blocks replication
The Cortex store-gateway (used only when Cortex is running with the blocks storage) supports blocks sharding, used to horizontally scale blocks in a large cluster without hitting any vertical scalability limit.
To enable the zone-aware replication for the store-gateways, please refer to the store-gateway documentation.
Minimum number of zones
For Cortex to function correctly, there must be at least the same number of availability zones as the replication factor. For example, if the replication factor is configured to 3 (default for time-series replication), the Cortex cluster should be spread at least over 3 availability zones.
It is safe to have more zones than the replication factor, but it cannot be less. Having fewer availability zones than replication factor causes a replica write to be missed, and in some cases, the write fails if the availability zones count is too low.
Impact on unbalanced zones
Cortex requires that each zone runs the same number of instances of a given service for which the zone-aware replication is enabled. This guarantees a fair split of the workload across zones.
On the contrary, if zones are unbalanced, the zones with a lower number of instances would have an higher pressure on resources utilization (eg. CPU and memory) compared to zones with an higher number of instances.
Impact on costs
Depending on the underlying infrastructure being used, deploying Cortex across multiple availability zones may cause an increase in running costs as most cloud providers charge for inter availability zone networking. The most significant change would be for a Cortex cluster currently running in a single zone.