Azure service fabric node instance count doubles when cluster is created using ARM
I am experimenting with creating a new cluster using the ARM template and changing the template to add certificates, etc. The cluster and all resources were successfully created, but I noticed that initially the number of node instances is 2x, plus 1 than I am. For example, if I set "vmInstanceCount" to 3, I see that 7 instances are currently being created.
But if I just wait and let them finish, then 4 copies have been deleted and it will keep three copies. One problem is that it randomly chooses what to store, so the names to store might be nodes_1, node_4, node_6, which are dirty.
Here's my nodeType snippet:
"nodeTypes": [
{
"name": "[variables('vmNodeType0Name')]",
"applicationPorts": {
"endPort": 30000,
"startPort": 20000
},
"clientConnectionEndpointPort": "[variables('fabricTcpGatewayPort')]",
"ephemeralPorts": {
"endPort": 65534,
"startPort": 49152
},
"httpGatewayEndpointPort": "[variables('fabricHttpGatewayPort')]",
"isPrimary": true,
"vmInstanceCount": "[variables('vmInstanceCount')]",
"reverseProxyEndpointPort": "[variables('reverseProxyEndpointPort')]",
"durabilityLevel": "Bronze"
}
]
...
"sku": {
"name": "[variables('vmssSkuName')]",
"capacity": "[variables('vmssSkuCapacity')]",
"tier": "Standard"
}
source to share
I've talked to Microsoft before and this issue is actually a new feature as we can see here https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale -sets-design-overview # overprovisioning I'll close this question when I find an answer. However, I am still worried about naming, but I will pose this question to MS.
source to share