问题描述
每当我尝试解析无状态服务的端点时，我似乎总是会收到找不到服务"的消息.我尝试使用服务分区解析器和服务代理，但是它们都产生相同的结果. Service Fabric是否受到限制?或者我是否误解了应如何使用无状态服务?我找不到任何说明这两种方式的文档.
I seem to keep getting "Service Not Found" whenever I try to resolve an endpoint for a stateless service. I have tried using the service partition resolver and also the service proxy but they both yield same results. Is there a restriction on Service Fabric or am I misunderstanding how stateless services should be used? I could not find any documentation stating either way.
提供有关我正在尝试执行的操作的更多详细信息.我正在构建一个Api网关. Api网关由RegistryService和RoutingService组成.
To give more detail on what I am attempting to do. I am building an Api Gateway. The Api Gateway is comprised of RegistryService and a RoutingService.
我有多个服务结构应用程序，其中一些具有使用WebApi和Owin的前端"无状态服务.在启动时，这些服务将注册其路由到RegistryService.
I have multiple service fabric applications, some of which have "front-end" stateless services which use WebApi and Owin. On startup these services register their routes to the RegistryService.
网关使用Registryservices确定将请求定向到的服务.在这一点上，我正在尝试解析所述服务的端点，但未能解决.但是，如果我将路由更改为有状态的后端服务，则可以正常工作.
The Gateway uses the Registryservices to determine the service to direct the request to. At which point I am trying to resolve the endpoint of said services but fail to do so. If however I change my routing to stateful backend services it works fine.
任何想法都会很有帮助
推荐答案
因此，对于任何其他来这里的人也是如此.似乎这不是一个问题.重置SF群集即可修复它.
So for anyone else who comes along here. Seems like it was a non issue. Resetting the SF cluster fixed it.
这篇关于Service Fabric中无状态服务的服务解析器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！