azure-service-fabric

In Service Fabric, can I alter the Arguments in the ServiceManifest.xml file using Application Parameters?

守給你的承諾、 提交于 2019-12-01 11:02:55
I have an ApplicationManifest.xml file that looks like: <?xml version="1.0" encoding="utf-8"?> <ApplicationManifest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2011/01/fabric" ApplicationTypeName="ServiceFabricTestType" ApplicationTypeVersion="1.9"> <Parameters> <Parameter Name="Prop_BehavioursPath" DefaultValue="behaviours.yml"/> <Parameter Name="Prop_AliasesPath" DefaultValue="aliases.yml"/> </Parameters> <ServiceManifestImport> <ServiceManifestRef ServiceManifestName="SummaryGenerator"

Error while upgrading Azure Service Fabric through VSTS CI/CD

爱⌒轻易说出口 提交于 2019-12-01 11:01:34
I am using VSTS to setup CI/CD for service fabric build and deployment. First deploy goes through without error but second update deployment gives me below error. The content in ConfigPackage Name:Config and Version:1.0.0.20180312.1 in Service Manifest 'SampleWebPkg' has changed, but the version number is the same. I followed the below instruction https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-tutorial-deploy-app-with-cicd-vsts This happens because you have updated the service binaries and didn't update the manifests, the manifest points to the same version as before but

Register-ServiceFabricApplicationType on a secure cluster always times out

回眸只為那壹抹淺笑 提交于 2019-12-01 09:56:52
问题 When this command is executed while connected to a secure cluster: Register-ServiceFabricApplicationType -ApplicationPathInImageStore 'MyType' -TimeoutSec 600 -Debug -Verbose ...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. Stack trace: VERBOSE: System.TimeoutException:

Sending request to ASP.Net Core Web API running on a specific node in a Service Fabric Cluster

为君一笑 提交于 2019-12-01 09:37:44
I am working on a Service Fabric Application, in which I am running my Application that contains a bunch of ASP.NET Core Web APIs. Now when I run my application on my local service fabric cluster that is configured with 5 nodes, the application runs successfully and I am able to send post requests the exposed Web APIs. Actually I want to hit the code running on a same cluster node with different post requests to the exposed APIs on that particular node. For further explanation, for example there is an API exposed on Node '0' that accept a post request and execute a Job, and also there is an

SignalR with Service Fabric Stateless Web API

孤人 提交于 2019-12-01 09:06:07
问题 Got some info from this related question: Using SignalR with Azure Service Fabric Quote in quote from that comment history: "After deploying this application, you can see that some calls to signalR fails and Some succeeds...." Just want to know if anybody had similar implementation (signalR with Web API...). And I don't want to set instance count 1 for the stateless Web API. 回答1: You can configure LoadBalancer that is used by Service Fabric to persist session. This will result in particular

Load balancing a service fabric StatelessService with ServicePartitionClient

旧时模样 提交于 2019-12-01 08:50:02
I'm implementing an API gateway on a service fabric cluster where the API gateway service is the public endpoint that routes external HTTP requests into a set of worker services running in the cluster. For inter-service communication between the gateway and the internal services, we're using the ServicePartitionClient. I've found that when using the ServicePartitionClient to resolve service addresses and communicate with an stateless service, it will pick a single instance of the stateless service and only communicate with that one instance with every communication attempt. In my case, I have

Error while upgrading Azure Service Fabric through VSTS CI/CD

佐手、 提交于 2019-12-01 08:08:05
问题 I am using VSTS to setup CI/CD for service fabric build and deployment. First deploy goes through without error but second update deployment gives me below error. The content in ConfigPackage Name:Config and Version:1.0.0.20180312.1 in Service Manifest 'SampleWebPkg' has changed, but the version number is the same. I followed the below instruction https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-tutorial-deploy-app-with-cicd-vsts 回答1: This happens because you have updated

Load balancing a service fabric StatelessService with ServicePartitionClient

混江龙づ霸主 提交于 2019-12-01 06:52:10
问题 I'm implementing an API gateway on a service fabric cluster where the API gateway service is the public endpoint that routes external HTTP requests into a set of worker services running in the cluster. For inter-service communication between the gateway and the internal services, we're using the ServicePartitionClient. I've found that when using the ServicePartitionClient to resolve service addresses and communicate with an stateless service, it will pick a single instance of the stateless

How to enumerate all partitions and aggregate results

做~自己de王妃 提交于 2019-12-01 06:24:14
I have a multiple partitioned stateful service. How can I enumerate all its partitions and aggregate results, using service remoting for communication between client and service? You can enumerable the partitions using FabricClient : var serviceName = new Uri("fabric:/MyApp/MyService"); using (var client = new FabricClient()) { var partitions = await client.QueryManager.GetPartitionListAsync(serviceName); foreach (var partition in partitions) { Debug.Assert(partition.PartitionInformation.Kind == ServicePartitionKind.Int64Range); var partitionInformation = (Int64RangePartitionInformation