azure-service-fabric

问题 Most examples about service fabric shows that after deployments, cluster endpoints appear magically just as given in service-manifest eg: <cluster-url>:port/api/home Some people on forums mention about tweaking load balancer to allow access to port. Why the difference in opinions? Which way is correct? When I tried I was never able to access a deployed api/endpoint in azure cluster(load balancer tweaked or not). OneBox worked though. 回答1: The main detail most people forget when building SF

问题 I am trying to setup a docker image for an mvc5 website to deploy to my service fabric Windows server 2016 with containers based cluster. It seems that every image with IIS configured is based on a different windows build than 14393, and when I deploy those to service fabric they fail to start on my windows servers. Am I missing something here? Does it matter what server the dockerfile runs on? So far is seems impossible to get a simple site up and running in a docker container on my service

问题 I know that actors inside Service Fabric are single-threaded. But suppose I start a new thread inside an actor method, what will happen then? Will an actor be deactivated even though the spawned thread is still executing? According to the documentation, an actor is deactivated when it has not been 'used' for some time. 'Used' in this context means either: receiving a call IRemindable.ReceiveReminderAsync being invoked So it seems that the new thread I started is not taken into account. But

问题 I am getting the following exception when starting a Stateful Service which prevents the service from fully starting. How do I resolve this exception and get the service to start? System.InvalidCastException HResult=0x80004002 Message=Unable to cast COM object of type 'System.__ComObject' to interface type 'IFabricNodeContextResult2'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{472BF2E1-D617-4B5C-A91D-FABED9FF3550}' failed due to the

问题 In my WebApi I want to subscribe to the ActorEvents for all of my ActorIds. Subscribing to a single ActorId is easy, and works. However, I'm wondering if there is a way to subscribe everything all and future ones at once, that I might've missed in the documentation. Currently, I'm iterating through all my ActorIds on WebApi startup and subscribing. I then subscribe to new Ids, and unsubscribe from deleted ones. However, this is somewhat cumbersome, and since it is during startup, will throw

问题 I am just looking for a bit of advice about how to go about the title to this question. I currently have an asp.net core application which is backed by entity framework using DDD pattern that we are looking to migrate to a microservices architecture with service fabric. I am aware that actors can be persisted to disk and to memory, but does anyone have any experience with actors being persisted to an external storage such as MSSQL? The reason this comes about is that currently we run into

问题 As per this page, node types in service fabric can be seen as analogous to roles in cloud services. If that is the case, then how do we think about deploying multiple applications to same service fabric cluster. E.g. let's say there are 2 applications: The first only needs a web role, The seconds, which needs 1 web role and 2 worker roles. Questions: Then do we create service fabric cluster with 3 node types (web-1, worker-1, worker-2) and then let web roles of both apps share web-1 node type

问题 I created a Azure Service Fabric Web API and planned to reach it through Service Fabric's built in Reverse Proxy. All was working well locally but when I published to Azure, trying to access the route through Reverse Proxy would time out. I thought it might be my app, so I just popped open a new solution with the default template and published to my local. Everything worked fine Reverse Proxy and all. So I published to Azure and again had the same issue. I could access the Web API on azure

问题 I have incremented the version of one of the services in my Service Fabric application. However, when I try to upgrade the cluster I get the error below: The content in CodePackage Name:Code and Version:1.0.0 in Service Manifest 3>'MYAPPLICATION.ServiceFabricPkg' has changed, but the version number is the same. 3>At C:\Program Files\Microsoft SDKs\Service 3>Fabric\Tools\PSModule\ServiceFabricSDK\Publish-UpgradedServiceFabricApplication.ps1:135 char:38 This is a huge issue for me as one of the

问题 When i Am clicking Publish It is showing Following Powershell Error: 回答1: Finally Found the solution Created a new azure cluster and deployed to it and it worked! 来源： https://stackoverflow.com/questions/44384647/not-able-to-publish-azure-service-to-remote-cluster