azure-service-fabric

I have a stateless ASP.NET Core (RC1) service running in my Azure Service Fabric cluster. It has the following manifest: <ServiceManifest Name="MyServicePkg" Version="1.0.2" ...> <ServiceTypes> <StatelessServiceType ServiceTypeName="MyServiceType" /> </ServiceTypes> ... </ServiceManifest> My cluster is configured with placement properties. I have 5 servers with "nodeType=Backend" and 3 servers with "nodeType=Frontend". I would like to upgrade my Service and specify that it may only be placed on "Backend" nodes. This is my updated manifest: <ServiceManifest Name="MyServicePkg" Version="1.0.3" .

I created a stateless service in service fabric local cluster with Visual studio 2017. It came with a predefined random port 8462. I changed the port in the ServiceManifest.xml to another, but every time I launch the project it goes to the old port, I can see in the Output " Launching the browser with URL http://localhost:8462/ to open the application. " and I have to change it manually. Ho I change the default launch url? in the project properties there is no option. Thanks Right click the Service Fabric Application project (so, not the project of a service) and select "properties". You can

When opening a sql connection to a local database in a traditional console app I have no issues, however when I attempt to do the same thing within a stateless service running in Service Fabric I get a login error. The error I receive is "Login failed for user 'WORKGROUP\\NICK$'." And this is the code I'm using to connect using (var con = new SqlConnection("Server=.;Trusted_Connection=True;Database=AddressBook")) { try { con.Open(); } catch (Exception e) { } } When I try to add that user to sql server it tells me that the user cannot be found. Based on the comments above I learned that Service

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

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: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF

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. You can configure LoadBalancer that is used by Service Fabric to persist session. This will result in particular client ending up always in the same node. You can do it by accessing LoadBalancer assigned to service fabric