An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
Hello @Hiral Shah ,
Every node in the dedicated SQL pool is designed with HA in mind – meaning, in case of node level failures, new nodes will be brought as replacements automatically. However, this is happening at the infrastructure level – users will experience this failure as something that will break user apps (and queries/workloads) as instance will be unavailable until system heals fully.
In Gen3 workload level resilience is not dependent on multi-cluster feature, it is intrinsic to life cycle of a query on any pool – we have resilience for BE node failures (DQP performs task retry), and for DQP failures (FE performs query retry through DQP-client gRPC protocol). On FE failure we lose the client connection, and we have no workload resilience to these types of failures. The user will be able to reconnect once the FE is back up, which as you said it should be a fast fail-over that our infra takes care of.
Hope this helps. Do let us know if you any further queries.
------------
Please don’t forget to Accept Answer and Up-Vote wherever the information provided helps you, this can be beneficial to other community members.