Stop-ServiceFabricNode cmdlet 导致 Azure Service Fabric 集群连接不响应
Stop-ServiceFabricNode cmdlet causes Azure Service Fabric Cluster connection to not respond
我想停止我拥有的服务结构集群资源之一（有 5 个节点）的节点，所以我使用了 Stop-ServiceFabricNode。我成功地为 3 个节点执行了此操作，第 4 个节点导致我的 PowerShell ISE 挂起，我不得不中途取消它。之后我无法连接到我的服务结构实例。
当我尝试使用 Connect-ServiceFabricCluster 时，我收到错误提示：
WARNING: Failed to contact Naming Service. Attempting to contact Failover Manager Service...
WARNING: Failed to contact Failover Manager Service, Attempting to contact FMM...
False
WARNING: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed becau
se connected host has failed to respond <IP>
Connect-serviceFabricCluster : No cluster endpoint is reachable, please check if there is connectivity/firewall/DNS issue.
At line:1 char:1
+ Connect-serviceFabricCluster -ConnectionEndpoint "<resourcename>.w ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Connect-ServiceFabricCluster], FabricException
+ FullyQualifiedErrorId : TestClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.ConnectCluster
请告诉我如何重新启用连接。
您通过 PowerShell 与之通信的 REST api 在您已关闭的节点上运行。在某些时候它们不再可用：
The Stop-ServiceFabricNode cmdlet stops the node that you specify with
the NodeName parameter by stopping the Fabric.exe process, which stops
all of the system service and user service replicas hosted on that
Service Fabric node.
以下选项之一可能有效。希望选项 1：
- 在所有停止的节点中执行 RDP 并执行
Start-SeviceFabricNode script，IpAddressOrFQDN 和 ClusterConnectionPort 指向节点 ip 地址和端口。
The Start-ServiceFabricNode cmdlet starts the node specified by the
NodeName parameter that has been stopped using the
Stop-ServiceFabricNode cmdlet
危险区域：
- 从 Azure 门户重新启动 VM 规模集。 可能会导致数据丢失
- 从 Azure 门户重新分配您的 VM 规模集。 会造成数据丢失
- 重新创建集群会导致数据丢失
我想停止我拥有的服务结构集群资源之一（有 5 个节点）的节点，所以我使用了 Stop-ServiceFabricNode。我成功地为 3 个节点执行了此操作，第 4 个节点导致我的 PowerShell ISE 挂起，我不得不中途取消它。之后我无法连接到我的服务结构实例。
当我尝试使用 Connect-ServiceFabricCluster 时，我收到错误提示：
WARNING: Failed to contact Naming Service. Attempting to contact Failover Manager Service...
WARNING: Failed to contact Failover Manager Service, Attempting to contact FMM...
False
WARNING: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed becau
se connected host has failed to respond <IP>
Connect-serviceFabricCluster : No cluster endpoint is reachable, please check if there is connectivity/firewall/DNS issue.
At line:1 char:1
+ Connect-serviceFabricCluster -ConnectionEndpoint "<resourcename>.w ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Connect-ServiceFabricCluster], FabricException
+ FullyQualifiedErrorId : TestClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.ConnectCluster
请告诉我如何重新启用连接。
您通过 PowerShell 与之通信的 REST api 在您已关闭的节点上运行。在某些时候它们不再可用：
The Stop-ServiceFabricNode cmdlet stops the node that you specify with the NodeName parameter by stopping the Fabric.exe process, which stops all of the system service and user service replicas hosted on that Service Fabric node.
以下选项之一可能有效。希望选项 1：
- 在所有停止的节点中执行 RDP 并执行
Start-SeviceFabricNodescript，IpAddressOrFQDN 和 ClusterConnectionPort 指向节点 ip 地址和端口。
The Start-ServiceFabricNode cmdlet starts the node specified by the NodeName parameter that has been stopped using the Stop-ServiceFabricNode cmdlet
危险区域：
- 从 Azure 门户重新启动 VM 规模集。 可能会导致数据丢失
- 从 Azure 门户重新分配您的 VM 规模集。 会造成数据丢失
- 重新创建集群会导致数据丢失