service-fabric-stateful

Azure Service Fabric InvokeWithRetryAsync huge overhead

假装没事ソ 提交于 2019-12-08 11:10:45
问题 I'm currently working on a Service Fabric microservice which needs to have a high throughput. I wondered why I'm not able to achieve more than 500 1KB messages per second on my workstation using loopback. I removed all the business logic and attached a performance profiler, just to measure end to end performance. It seems that ~96% of the time is spent resolving the Client and only ~2% doing the actual Http requests. I'm invoking "Send" in a tight loop for the test: private

Deploy a C# Stateful Service Fabric application from Visual Studio to Linux

99封情书 提交于 2019-12-07 04:57:21
问题 EDIT 04/06/18 => Updated question with last status So I have this working .Net 4.6 Stateful Service that currently run on my Windows Service Fabric cluster deployed on Azure. Starting from 09/2017, I should be able to move to Linux: https://blogs.msdn.microsoft.com/azureservicefabric/2017/09/25/service-fabric-6-0-release/ So I'm trying to deploy it on Linux so I can save costs. First things first, I've migrated all my code from .Net 4.6 to .Net Core 2.0. Now I can compile my binaries without

Deploy a C# Stateful Service Fabric application from Visual Studio to Linux

ぃ、小莉子 提交于 2019-12-05 07:04:58
EDIT 04/06/18 => Updated question with last status So I have this working .Net 4.6 Stateful Service that currently run on my Windows Service Fabric cluster deployed on Azure. Starting from 09/2017, I should be able to move to Linux: https://blogs.msdn.microsoft.com/azureservicefabric/2017/09/25/service-fabric-6-0-release/ So I'm trying to deploy it on Linux so I can save costs. First things first, I've migrated all my code from .Net 4.6 to .Net Core 2.0. Now I can compile my binaries without issues. I've basically created new .Net Core projects and then moved all my source code from .Net 4.6

Service Resolver for Stateless Services in Service Fabric

大城市里の小女人 提交于 2019-12-04 20:27:09
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. 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. I have multiple service fabric applications, some of which have "front

What do the EndPoints configure in the ServiceManifest of an Service Fabric Service?

家住魔仙堡 提交于 2019-12-04 17:45:18
We have a Service Fabric Service project with multiple services: Actors, Stateful services and Stateless services combined into one ServiceManifest. Two stateful services did not work: the constructors were called, the communicationlisteners (through remoting) were created, but the RunAsync method was not called. After removing the endpoint listing from the ServiceManifest.xml the services started working again. But now we are left wondering why and how this works. Could someone explain? To illustrate, the relevant section was <Resources> <Endpoints> <Endpoint Name="WebServiceEndpoint" Type=

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 Actor or Service Becomes Inaccessible at Random after Upgrading to SDK 2.3.301

﹥>﹥吖頭↗ 提交于 2019-12-03 09:04:08
问题 After upgrading from Service Fabric SDK 2.0.135 to 2.3.301, we have started encountering situations where a Service Fabric actor or service is inaccessible in spite of showing as healthy in Service Fabric Explorer. Once in this state, any call to the actor or service via the ActorProxy or ServiceProxy will hang for 5 minutes before finally giving a TimeoutException. Once in this state, the actor or service never recovers on its own – even if left for an hour. The only solution is to reset the

Service Fabric Stateful Service Remoting V2

别等时光非礼了梦想. 提交于 2019-12-03 06:53:30
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 the example is for the stateless one. I tried to change the code in this without success. protected

store cancellation tokens in service fabric services

半腔热情 提交于 2019-12-01 14:22:29
I am trying to achieve cancel tasks feature in service fabric stateful services. Plan is using cancellation token to propagate notices to linked threads / Tasks. The problem is, while there are these long running tasks and threads waiting for this signal, I am not sure how I can find the right cancellation tokens based on another Web API calls. I was thinking of using reliable dictionary, then even before trying it out, I assume this will hit deadend because cancellationToken can't be serialized / deserialized. Please help me what could be good solution to solve this issue. Update (I didn't

store cancellation tokens in service fabric services

故事扮演 提交于 2019-12-01 12:47:14
问题 I am trying to achieve cancel tasks feature in service fabric stateful services. Plan is using cancellation token to propagate notices to linked threads / Tasks. The problem is, while there are these long running tasks and threads waiting for this signal, I am not sure how I can find the right cancellation tokens based on another Web API calls. I was thinking of using reliable dictionary, then even before trying it out, I assume this will hit deadend because cancellationToken can't be