安全群集上的Register-ServiceFabricApplicationType总是超时 [英] Register-ServiceFabricApplicationType on a secure cluster always times out

问题描述

在连接到安全集群时执行此命令:

When this command is executed while connected to a secure cluster:

Register-ServiceFabricApplicationType -ApplicationPathInImageStore 'MyType' -TimeoutSec 600 -Debug -Verbose 

...它引发超时异常.我可以毫无问题地运行Copy-ServiceFabricApplicationPackage，因此显然可以连接到集群.

...it throws a timeout exception. I can run Copy-ServiceFabricApplicationPackage without problems, so it's clearly possible to connect to the cluster.

注册应用程序类型实际上并不是一项繁重的工作，因此，我怀疑存在一些潜在的问题.

Registering an app type shouldn't really be a heavy operation, I therefore suspect that there is some underlying problem.

堆栈跟踪:

VERBOSE: System.TimeoutException: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF
   at System.Fabric.Interop.NativeClient.IFabricApplicationManagementClient6.EndProvisionApplicationType(IFabricAsyncOperationContext context)
   at System.Fabric.Interop.Utility.<>c__DisplayClassa.<WrapNativeAsyncInvoke>b__9(IFabricAsyncOperationContext context)
   at System.Fabric.Interop.AsyncCallOutAdapter2`1.Finish(IFabricAsyncOperationContext context, Boolean expectedCompletedSynchronously)
   --- End of inner exception stack trace ---
Register-ServiceFabricApplicationType : Operation timed out.
At line:1 char:1
+ Register-ServiceFabricApplicationType -ApplicationPathInImageStore 'M ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationTimeout: (Microsoft.Servi...usterConnection:ClusterConnection) [Register-ServiceFabricApplicationType], TimeoutException
    + FullyQualifiedErrorId : RegisterApplicationTypeErrorId,Microsoft.ServiceFabric.Powershell.RegisterApplicationType

任何帮助都将不胜感激！

Any help greatly appreciated!

推荐答案

在非常相似的情况下，这对我们有用:

Here's what worked for us in a very similar situation:

请在所有节点上应用以下缓解步骤(一次减少一个节点):

Please apply the following mitigation steps (one node at a time) on all nodes:

1. 转到群集的数据根，默认情况下为"D:\ SvcFab \" 或 C:\ ProgramData \ Microsoft \ SF (如果未指定)部署中的datapath属性.按名称查找文件夹.在该文件夹内，您将看到文件 Fabric.Package.current.xml .创建备份.
2. 打开Fabric.Package.current.xml文件，然后查找Fabric.Config版本:
3. 转到该版本的config文件夹，然后查找 Settings.xml 文件.
4. 备份Settings.xml文件并打开 Settings.xml 文件.
5. 查找名为"EseStore" 的部分.

1. Go to data root of cluster, by default it is "D:\SvcFab\" or C:\ProgramData\Microsoft\SF if you didn’t specify datapath attribute in deployment. Look for folder by name . Inside that folder you will see file Fabric.Package.current.xml. create a backup.
2. Open the Fabric.Package.current.xml file and look for Fabric.Config version:
3. Go to config folder for that version and look for Settings.xml file.
4. Take a backup of Settings.xml file and open the Settings.xml file.
5. Look for section named "EseStore".

<Section Name="EseStore">

</Section>

1. 如果存在节，则将此参数添加到节中(与复制粘贴相比，最好在 Settings.xml 文件中键入这些文本，因为复制粘贴有时会在末尾附加多余的无效字符).

1. If section is present, add this parameter to section (prefer to type these text in the Settings.xml file than copy-pasting as copy-pasting sometimes appends extra invalid characters at the end).

<Section Name="EseStore">
<Parameter Name="MaxCursors" Value="32768" />
</Section>

1. 如果不存在名称为"EseStore" 的部分，请添加参数为的部分名称并保存文件.
2. 在节点上杀死 FileStoreService.exe .
3. 等待 FileStoreService.exe 重新启动，然后继续下一个节点.

1. If the section with name "EseStore" is not present, add the section name with parameter as and save the file.
2. Kill FileStoreService.exe on the node.
3. Wait for the FileStoreService.exe to come back up and then proceed to next node.

在对所有节点应用缓解措施并且群集恢复正常之后，请重试部署该程序包.在生产中使用之前，请先确保先在测试机中进行测试.

After you are done applying mitigation to all nodes and cluster is back up healthy, please retry deploying the package. Please make sure for testing in testing machine first before use on production.

这篇关于安全群集上的Register-ServiceFabricApplicationType总是超时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！