Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Building a Hybrid Database-as-a-Service Platform with Azure Stack HCI
Overview Solution Architecture Lab Setup Performance-Oriented Test Scenarios Functional Test Scenarios
Functional testing methodology
Scale up Azure Arc-enabled SQL Managed Instances
Expand the Azure Stack HCI cluster
Scale out the AKS hybrid workload cluster
Full-stack life cycle management
Azure Stack HCI failure scenarios
Conclusion Appendix A: SQL MI and HammerDB Test Harness details Appendix B: HammerDB CLI configuration Additional Resources

Azure Stack HCI failure scenarios

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > White Papers > Building a Hybrid Database-as-a-Service Platform with Azure Stack HCI > Azure Stack HCI failure scenarios

Azure Stack HCI failure scenarios

  • In this final functional test, we forcibly removed power from one of the Azure Stack HCI cluster nodes, a7525r06c01n03. This server was running one AKS hybrid worker node VM in the dbaas-databases-1 workload cluster. Approximately four minutes after removing power, the worker node VM was restarted on a7525r06c01n02. All SQL MI pods running on the worker node VM prior to the power outage remained running on the same VM. This scenario is depicted in the following figure.

    A picture containing diagramDescription automatically generated

    Figure 37.    Azure Stack HCI cluster node failure scenario

    Then, we forcibly powered off the worker node VM on a7525r06c01n03. In this case, the SQL MI pods were re-created on another worker node in the dbaas-databases-1 workload cluster. This scenario is depicted in the following figure.

    Graphical user interface, applicationDescription automatically generated

    Figure 38.    AKS hybrid worker node failure