Deploy SF Cluster acroos availabiliti zones by pinning one virtual machine scale set to each zone

yeswanth 1 Reputation point
2021-11-02T18:40:13.157+00:00

As per documentation,

The recommended topology for the primary node type requires this:

Three node types marked as primary
Each node type should be mapped to its own virtual machine scale set located in a different zone.
Each virtual machine scale set should have at least five nodes (Silver Durability).

What is the distribution w.r.t to non-primary node types , are also suppose to be mapped to their own virtual scale set located in different zones ?

Azure Service Fabric
Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
252 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. vipullag-MSFT 24,441 Reputation points
    2021-12-02T07:37:45.69+00:00

    @yeswanth

    Apologies in delayed response on this.

    You can consider using the newer Service Fabric Managed Cluster across availability zones, this is a much simpler model and allows a lot lower minimums if that is desired.

    Also, you can check this zone spanning scale sets option here.

    Currently with cross AZ testing for your environment below are few suggestions:

    As you already have single AZ cluster(s) and looking to migrate to Cross AZ cluster(s)
    • Determine if moving to SFMC is an option.
    • If cross Az effort is in early stages of validation and production migration is 3-6 months away, consider using Az spanning VMSS for each node type.

    For your specific question to get cross AZ support without using Cross Az VMSS, following is required.
    • Follow the same recommendation specified for Primary node type for all other node types expect that you don’t to mark the other node types as Primary
    • Change placement constraints for service so they can be placed across zones

    In addition, below applies independent of which cross AZ solution you use.
    • For stateful services, you should increase target replica count to an odd multiple of number of zones i.e. 3, 9, 15
    o This will ensure that if one zone goes down there are sufficient remaining replicas to maintain quorum

    However, these features are in preview currently and not recommended for production workloads.

    Hope this helps.
    If the suggested response helped you resolve your issue, please 'Accept as answer', so that it can help others in the community looking for help on similar topics.

    0 comments No comments