azure-service-fabric

问题 I want to be able to configure placement constraints based on different node types (i.e. FrontEnd, BackEnd). Can I do this per-environment, so that in my test/local cluster there are no constraints, but on my production environments there is? 回答1: Yes, you can! The official docs describe a way to do this via code, but you can also do so with the service manifest files directly to get default & per-environment configuration. There is a blog post you can follow (found it in this answer). 来源：

问题 Is there any way to inject dependencies in to the Azure Service Fabric Actor's constructor? 回答1: Having had a bit of a dig-around in this area with dotPeek a while back (trying to resolve actors from an Autofac lifetime scope per-invocation), I think the trick is to create your own implementation of StatelessActorServiceFactory, and your own extension method to register the actor with it. Although the factory class is marked as internal, its interface (IStatelessServiceFactory) and the

问题 I need to implement pipeline if Service Fabric's Reliable Services, and I need some guidelines about what of these approaches is preferable from the viewpoint of reliability simplicity and simple good design: 回答1: I have been investigating this topic a lot as well (to be applied to my work for NServiceBus and MessageHandler) and would like to provide my thoughts on the matter. However I haven't determined what the best model is yet. If you disregard the practical implementation with

问题 How to create a deployment package for Service Fabric that includes all artifacts necessary to run the designed workflows at run-time? 回答1: Another option is to package a service fabric application by building a solution in release mode (for example). This section can be added to the .sfproj file to achieve the goal: <Target Name="ReleaseAfterBuild" AfterTargets="AfterBuild" Condition=" '$(Configuration)' == 'Release' "> <MSBuild Projects="$(ProjectPath)" Targets="Package" /> </Target> 回答2:

问题 Is it possible to use signalR with Service Fabric provided by Microsoft? I'm trying to connect an UWP app and an angularJS app to my stateless reliable service hosted in an Azure Cluster through signalR/websocket connection. But both are not able to open such a connection. On my local machine everything works fine. Is there anything special to consider of using signalR/websockets with Service Fabric? Is there any example? 回答1: You need to configure the load balancer to the client ip. Then the

问题 Is it possible to use signalR with Service Fabric provided by Microsoft? I'm trying to connect an UWP app and an angularJS app to my stateless reliable service hosted in an Azure Cluster through signalR/websocket connection. But both are not able to open such a connection. On my local machine everything works fine. Is there anything special to consider of using signalR/websockets with Service Fabric? Is there any example? 回答1: You need to configure the load balancer to the client ip. Then the

问题 I'm trying to start application upgrade using Start-ServiceFabricApplicationUpgrade command, but getting an error complaining: Default service descriptions must not be modified as part of upgrade. Modified default service: ... None of the service configurations was changed. Also upgrade works fine when deployed from Visual Studio. Update: It turns out that parameters used in DefaultServices section of application manifest must be provided by -ApplicationParameter<Hashtable> command parameter

问题 I am working on Asp.Net core with Azure service fabric. We have stateless service too. On the Azure portal we have 5 nodes and for each node we have 2 instances. I have implemented logging mechanism. I am using Dependency injection too. Whenever worker role pick up the record from database,there are few values till the time that record is processed because I need to log those values in my logging framework. I am using this value to track telemetry across all systems. Currently I have created

问题 I use Deploy Compose Application to Service Fabric to deploy containers with VSTS on Service Fabric . My build agent had Service Fabric SDK 2.7. As soon as I upgrade it to 2.8 or 3.0, the VSTS task breaks with The ServiceDnsName for DefaultService 'xxx' is invalid 回答1: I cloned vsts-tasks, debugged ServiceFabricCompose and found out that UI parameter Application Name is placed into New-ServiceFabricComposeDeployment -DeploymentName . For old SDK 2.7 we had "fabric:/XYZ" in Application Name .

问题 The following post (on stackoverflow.com): Design of Application in Azure Service Fabric suggested that it is possible to have side by side installation of same application type with a different version. I tried to install a new version of application (fabric:/ServiceFabApp1 with a new version of 2.0.0 and of ServiceFabApp1Type) on my local cluster (that already has same application name with same application type with version 1.0.3 i.e. fabric:/ServiceFabApp1 with a existing version of 1.0.3