the database is distributed across the cluster, there is no single master node. You must open an elevated PowerShell prompt and execute the Get-NetworkControllerNode cmdlet to query the overall Service Fabric health and identify the explicitly out-of-sync nodes.
To safely resynchronize the cluster, you must forcefully clean the corrupted state from the broken nodes. Execute the Repair-NetworkControllerNode cmdlet targeting the unhealthy controllers. This safely evicts the node, clears the local database corruption, and automatically triggers a fresh synchronization from the nodes that still maintain quorum. If your cluster has suffered a complete loss of quorum, the underlying Service Fabric ring is broken and cannot self-heal. You must deploy a fresh Network Controller cluster and restore your authoritative network state from a backup or have your management plane, such as System Center Virtual Machine Manager, push the configuration down again.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN