You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/energy-data-services/reliability-energy-data-services.md
+4-113Lines changed: 4 additions & 113 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,15 +60,13 @@ The "X" part should identify the product or service.
60
60
Required: Provide an introduction. Use the following placeholder as a suggestion, but elaborate.
61
61
-->
62
62
63
-
This article describes reliability support in Microsoft Energy Data Services, and covers regional resiliency with [availability zones](#availability-zone-support). For a more detailed overview of reliability in Azure, see [Azure reliability](https://docs.microsoft.com/azure/architecture/framework/resiliency/overview.md).
63
+
This article describes reliability support in Microsoft Energy Data Services, and covers intra-regional resiliency with [availability zones](#availability-zone-support). For a more detailed overview of reliability in Azure, see [Azure reliability](https://docs.microsoft.com/azure/architecture/framework/resiliency/overview.md).
64
64
65
65
## Availability zone support
66
66
<!-- IF (AZ SUPPORTED) -->
67
-
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 the 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 [Regions and availability zones](/azure/availability-zones/az-overview.md).
67
+
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. If there's a local zone failure, availability zones are designed so that if the 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 [Regions and availability zones](/azure/availability-zones/az-overview.md).
68
68
69
-
Azure availability zones-enabled services are designed to provide the right level of reliability and flexibility. They can be configured in two ways. They can be either zone redundant, with automatic replication across zones, or zonal, with instances pinned to a specific zone. You can also combine these approaches. For more information on zonal vs. zone-redundant architecture, see [Build solutions with availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability).
70
-
71
-
Microsoft Energy Data Services Preview supports zone-redundant instance by default and there is no setup required by the Customer.
69
+
Microsoft Energy Data Services Preview supports zone-redundant instance by default and there's no setup required by the Customer.
72
70
73
71
### Prerequisites
74
72
@@ -79,115 +77,8 @@ The Microsoft Energy Data Services Preview supports availability zones in the fo
79
77
| South Central US | North Europe ||||
80
78
| East US | West Europe ||||
81
79
82
-
### Zonal failover support
83
-
N/A
84
-
85
-
<!-- 3D. Zonal failover support --------------------------------------------------------
86
-
-->
87
-
88
-
<!-- IF (SERVICE IS ZONAL) -->
89
-
90
-
<!-- Indicate here whether the customer can set up resources of the service to failover to another zone. If they can set up failover resources, provide a link to documentation for this procedure. If such documentation doesn't exist, create the document, and then link to it from here. -->
91
-
92
-
<!-- END IF (SERVICE IS ZONAL) -->
93
-
94
-
### Fault tolerance
95
-
To prepare for availability zone failure, Microsoft Energy Data Services will over-provision capacity of service to ensure that the solution can tolerate ⅓ loss of capacity and continue to function without degraded performance during zone-wide outages.
To prepare for availability zone failure, customers should over-provision capacity of service to ensure that the solution can tolerate ⅓ loss of capacity and continue to function without degraded performance during zone-wide outages. Provide any information as to how customers should achieve this.
99
-
-->
100
-
101
80
### Zone down experience
102
-
- During a zone-wide outage, no action is required during zone recovery, Offering will self-heal and re-balance itself to take advantage of the healthy zone automatically.
103
-
104
-
- During a zone-wide outage, the customer should expect brief degradation of performance, until the service self-healing re-balances underlying capacity to adjust to healthy zones. This is not dependent on zone restoration; it is expected that the Microsoft-managed service self-healing state will compensate for a lost zone, leveraging capacity from other zones.
105
-
106
-
- In a zone-wide outage scenario, users should experience no impact on provisioned resources in a zone-redundant deployment. During a zone-wide outage , customers should be prepared to experience brief interruption for communication to provisioned resources; this prompts re-try logic with appropriate intervals. New requests will be directed to healthy nodes with zero impact on user. During zone-wide outages, users will be able to create new offering resources; however, there could be capacity constraints, due to which the underlying resources will be scaled on a best-effort basis.
107
-
108
-
- All Microsoft Energy Data Services APIs may need to be retried for 5XX errors.
109
-
110
-
<!-- IF (SERVICE IS ZONE REDUNDANT) -->
111
-
112
-
<!-- 3F. Zone down experience ----------------------------------------------------------
113
-
Select the scenario that best describes customer experience or combine/provide your own description:
114
-
115
-
- During a zone-wide outage, no action is required during zone recovery, Offering will self-heal and re-balance itself to take advantage of the healthy zone automatically.
116
-
117
-
- During a zone-wide outage, the customer should expect brief degradation of performance, until the service self-healing re-balances underlying capacity to adjust to healthy zones. This is not dependent on zone restoration; it is expected that the Microsoft-managed service self-healing state will compensate for a lost zone, leveraging capacity from other zones.
118
-
119
-
- In a zone-wide outage scenario, users should experience no impact on provisioned resources in a zone-redundant deployment. During a zone-wide outage , customers should be prepared to experience brief interruption for communication to provisioned resources; typically, this is manifested by client receiving 409 error code; this prompts re-try logic with appropriate intervals. New requests will be directed to healthy nodes with zero impact on user. During zone-wide outages, users will be able to create new offering resources and successfully scale existing ones.
120
-
121
-
The table may contain:
122
-
123
-
- CRUD and Scale-out operations (Create Read Update Delete)
124
-
- Application communication scenarios – data plane operations (for example, insert/update/delete for a database).
125
-
126
-
| Operation name | Outage | Availability Impact | Durability Impact | Error code |What to do |
127
-
|--|--|--|--|--|
128
-
129
-
The table below lists all error codes that may be thrown by the Microsoft Energy Data Services and resources of that service during zone down outages.
130
-
131
-
List the following:
132
-
133
-
- CRUD and Scale-out operations (Create Read Update Delete)
134
-
- Application communication scenarios – data plane operations (for example, insert/update/delete for a database).
135
-
136
-
| Error code | Operation | Description |
137
-
|---|---|---|
138
-
-->
139
-
<!-- END IF (SERVICE IS ZONE REDUNDANT) -->
140
-
141
-
#### Zone outage preparation and recovery
142
-
<!-- TODO: Add your zone outage preparation and recovery -->
143
-
144
-
<!-- 3G. Zone outage preparation and recovery ------------------------------------------
145
-
The table below lists alerts that can trigger an action to compensate for a loss of capacity or a state for your resources. It also provides information regarding actions for recovery, as well as how to prepare for such alerts prior to the outage.
146
-
147
-
| Alert type | Actions for recovery | How to prepare prior to outage |
148
-
|--|--|--|
149
-
-->
150
-
151
-
### Low-latency design
152
-
Microsoft guarantees communication between zones of < 2ms and all underlying Microsoft Energy Data Services resources supports it.
<!-- Describe scenarios in which the customer will opt for zonal vs. zone-redundant version of your offering.-->
160
-
161
-
<!-- Microsoft guarantees communication between zones of < 2ms. In scenarios in which your solution is sensitive to such spikes, you should configure all components of the solution to align to a zone. This section is intended to explain how your service enables low-latency design, including which SKUs of the service support it. -->
162
-
163
-
<!-- OPTIONAL SECTION. If your service supports active-passive model, share an approach to control active component to a desired zone and align passive component with next zone. Make an explicit call-out for functionality where a resource is flagged as zone redundant but offers active-passive/primary-replica model of functionality-->
164
-
165
-
<!-- END IF (SERVICE IS ZONE REDUNDANT AND ZONAL) -->
166
-
167
-
168
-
<!-- ### Safe deployment techniques -->
169
-
<!-- TODO: Add your safe deployment techniques -->
If application safe deployment is not relevant for this resource type, explain why and how the service manages availability zones for the customer behind the scenes.
173
-
-->
174
-
175
-
<!-- When you opt for availability zones isolation, you should utilize safe deployment techniques for application code, as well as application upgrades. Describe techniques that the customer should use to target one-zone-at-a-time for deployment and upgrades (for example, virtual machine scale sets). If something is strictly recommended, call it out below. -->
176
-
177
-
<!-- List health signals that the customer should monitor, before proceeding with upgrading next set of nodes in another zone, to contain a potential impact of an unhealthy deployment. -->
178
-
<!-- [Health signals] -->
179
-
<!-- TODO: Add your health signals -->
180
-
181
-
<!-- ### Availability zone redeployment and migration -->
182
-
<!-- TODO: Add your availability zone redeployment and migration -->
183
-
184
-
<!-- 3J. Availability zone redeployment and migration ----------------------------------------------------
185
-
Link to a document that provides step-by-step procedures, using Portal, ARM, CLI, for migrating existing resources to a zone redundant configuration. If such a document doesn't exist, please start the process of creating that document. The template for AZ migration is:
During a zone-wide outage, no action is required during zone recovery. Customer may however experience brief degradation of performance, until the service self-heals and rebalances underlying capacity to adjust to healthy zones. Customers experiencing failures with Microsoft Energy Data Services APIs may need to be retried for 5XX errors.
0 commit comments