azure-service-fabric

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

爱⌒轻易说出口 提交于 2019-12-04 01:44:56
问题 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"/> <

How can I host multiple Service Fabric Actor Types inside a single service?

和自甴很熟 提交于 2019-12-04 00:36:13
问题 I've read here that is should be possible to host tightly coupled ActorTypes within the same service but I can't seem to find any documentation on exactly how to do it. I thought it might I need to create my own instance of the ActorService and pass the context into it but I don't seen to be able to find the right API's from the document. Does anyone have an example they could share ? 回答1: Sort of but not really. You can have multiple actor types in the same application . It looks like they

How to see if running under service fabric

冷暖自知 提交于 2019-12-04 00:29:05
I sometimes run projects locally out of visual studio is there a better way to detect if I'm hosted by SF rather than the exception. I can see possibly the path or entry assembly but there must be a better way. try { ServiceRuntime.RegisterServiceAsync("FisConfigUIType", context = > new WebHost < Startup > (context, loggerFactory, "ServiceEndpoint", Startup.serviceName)).GetAwaiter().GetResult(); Thread.Sleep(Timeout.Infinite); } catch (FabricException sfEx) { RunLocal(args, loggerFactory); } Check Service Fabric Environment Variables : var sfAppName = Environment.GetEnvironmentVariable(

libsodium-64.dll not found in production Azure Service Fabric cluster

大兔子大兔子 提交于 2019-12-03 21:29:04
问题 Using libsodium-net for all of its security goodness in an Azure Service Fabric Reliable Service, on my local dev cluster everything is working fine (although I did have to set the libsodium-64.dll to copy to the output directory). Unfortunately, when deployed to a real cluster in Azure it throws the following error: Unable to load DLL 'libsodium-64.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) I've checked by Remote Desktop-ing into one of the nodes and

Strategy to unprovision old applicationtype versions in Service Fabric

非 Y 不嫁゛ 提交于 2019-12-03 20:33:27
问题 Is there a way to set some sort of configuration on the cluster to remove service fabric application type versions? Like only keep the last 5 versions or something? For example i have CI/CD deploying new versions of a service fabric app to our cluster, it leaves a bunch of application version types in the cluster. Is there a way to automatically unprovision them over time or only keep a certain number of versions? 回答1: There are two options that cross my mind - Specify

Removing application from service fabric cluster

橙三吉。 提交于 2019-12-03 19:05:27
问题 I tried removing application from service fabric using service fabric explorer. I deleted my application using Delete Application action. Then When I tried Unprovision application type I got error saying, Error: Application Type of version 1.0.0 could not be unprovisioned as it still contains active applications. I could see that even after deleting the application , the actor service inside the application is still active in some of the nodes. Am attaching a screenshot of my service fabric

Azure Service Fabric usage

和自甴很熟 提交于 2019-12-03 18:11:00
问题 Service Fabric was just announced at the build conference. I was reading the scarce documentation about it and I have a question. I'm evaluating Service Fabric for hosting CRUD like microservices that are at the moment built in ASP.NET WebApi. Is Service Fabric geared towards hosting small pieces of functionality that receive data, process it and return the result, rather than hosting CRUD WebApi types of application? 回答1: Service Fabric enables the creation of both stateless and stateful

Service Fabric Stateful Service Remoting V2

£可爱£侵袭症+ 提交于 2019-12-03 17:49:48
问题 I have a Stateful Service called by a Stateless service, in .Net Standard Asp.net Core 2.0 running on Visual Studio 15.4. I can't make the Service Remoting V2 work. The old code in the Stateful service that worked for V1 is not valid anymore protected override IEnumerable<ServiceReplicaListener> CreateServiceReplicaListeners() { return new List<ServiceReplicaListener>() { new ServiceReplicaListener((context) =>this.CreateServiceRemotingListener(context)) }; I tried to follow this tutorial but

Service Fabric Service Remoting

回眸只為那壹抹淺笑 提交于 2019-12-03 17:25:33
I've been migrating from Cloud Services to Service Fabric the last few weeks and have been running into a few stumbling blocks using Remoting between 2 services. I've been using the official documentation and sample code on Service Remoting and in particular I'm trying to get the sample outlined here to work: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-communication-remoting I have 2 services. One is named "RemoteService" and the other is named "CallerService" . Both are derived from a default Stateless Service project. In both the "RemoteService" and

Service Fabric https endpoint with kestrel and reverse proxy

↘锁芯ラ 提交于 2019-12-03 17:02:29
I've been trying to setup Https on a stateless API endpoint following the instructions on the microsoft documentations and diverse post/blogs I could find. It works fine locally, but I'm struggling to make it work after deploying it on my dev server getting Browser : HTTP ERROR 504 Vm event viewer : HandlerAsyncOperation EndProcessReverseProxyRequest failed with FABRIC_E_TIMEOUT SF event table : Error while processing request: request url = https://mydomain:19081/appname/servicename/api/healthcheck/ping, verb = GET, remote (client) address = xxx, request processing start time = 2018-03-13T14