Skip to content

Commit ba1c7c2

Browse files
committed
edit
1 parent ad97403 commit ba1c7c2

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

articles/reliability/reliability-hdinsight.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -12,22 +12,17 @@ CustomerIntent: As a cloud architect/engineer, I need general guidance on migrat
1212

1313
# Reliability in Azure HDInsight
1414

15-
This article describes reliability support in Azure HDInsight and covers both intra-regional resiliency with [availability zones](#availability-zone-support)
16-
(#disaster-recovery-cross-region-failover). For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
15+
This article describes reliability support in Azure HDInsight, and covers [availability zones](#availability-zone-support). For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
1716

1817

1918
## Availability zone support
2019

2120
Azure availability zones are at least three physically separate groups of datacenters within each Azure region. Datacenters within each zone are equipped with independent power, cooling, and networking infrastructure. In the case of a local zone failure, availability zones are designed so that if one zone is affected, regional services, capacity, and high availability are supported by the remaining two zones. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see [Availability zone service and regional support](availability-zones-service-support.md).
2221

23-
An Azure HDInsight cluster consists of multiple nodes (head nodes, worker nodes, gateway nodes and zookeeper nodes). In a region that supports availability zones, HDInsight by default automatically spreads the cluster nodes across all zones of the selected region. In this default deployment model, you choose to have no control over which cluster nodes are provisioned in which availability zone.
24-
25-
However, Azure HDInsight also supports both [zone-redundant and zonal deployment configurations](availability-zones-service-support.md#azure-services-with-availability-zone-support).
26-
27-
- **Zonal**. Azure HDInsight cluster nodes are placed in a single zone that you select in the selected region. A zonal HDInsight cluster is isolated from any outages that occur in other zones. However, if an outage impacts the specific zone chosen for the HDInsight cluster, the cluster won't be available. This deployment model provides inexpensive, low latency network connectivity within the cluster. Replicating this deployment model into multiple availability zones can provide a higher level of availability to protect against hardware failure.
28-
29-
- **Zone-redundant**. If you want application requires availability across multiple availability zones, you can create one primary HDInsight cluster in one availability zone and create a secondary HDInsight cluster in a different availability zone with minimum size to save cost. With this design, if one of the other availability zones goes down, this HDInsight cluster won’t be impacted. If this availability zone goes down, customers need to switch the secondary clusters in a different availability zone to the primary, route the workload to this new primary cluster, and quickly scale up the cluster size to pick up the data processing.
22+
Azure HDInsight supports a [zonal deployment configuration](availability-zones-service-support.md#azure-services-with-availability-zone-support). Azure HDInsight cluster nodes are placed in a single zone that you select in the selected region. A zonal HDInsight cluster is isolated from any outages that occur in other zones. However, if an outage impacts the specific zone chosen for the HDInsight cluster, the cluster won't be available. This deployment model provides inexpensive, low latency network connectivity within the cluster. Replicating this deployment model into multiple availability zones can provide a higher level of availability to protect against hardware failure.
3023

24+
>[!IMPORTANT]
25+
>For deployments where users don't specify a specific zone, node types are not zone resilient and can experience downtime during an outage in any zone in that region.
3126
3227
## Prerequisites
3328

@@ -104,7 +99,7 @@ You can scale up an HDInsight cluster with more worker nodes. The newly added wo
10499

105100
### Availability zone redeployment
106101

107-
Azure HDInsight clusters currently doesn't support in-place migration of existing cluster instances to availability zone support. However, you can choose to [recreate your cluster](#create-an-hdinsight-cluster-using-availability-zone), and choose availability zone support during the cluster creation.
102+
Azure HDInsight clusters currently doesn't support in-place migration of existing cluster instances to availability zone support. However, you can choose to [recreate your cluster](#create-an-hdinsight-cluster-using-availability-zone), and choose a different availability zone or region during the cluster creation. A secondary standby cluster in a different region and a different availability zone can be used in disaster recovery scenarios.
108103

109104
### Zone down experience
110105

0 commit comments

Comments
 (0)