azure-service-fabric

问题 We have a stateless Java Application which I want to be deployed in Azure fabric. I have installed the Fabric SDK and Visual studio tools as per the documentation. After that I have created the Service Fabric application "Guest Executable" template and my project structure is like below: I have followed steps similar to the documentation as in https://azure.microsoft.com/en-us/documentation/articles/service-fabric-deploy-existing-app/ My ServiceManifest.xml is below: <?xml version="1.0"

问题 How to access a "Service Remoting V2" Service outside Service Fabric Cluster? 回答1: SF Remoting is intended to work within the cluster. You can use WCF communication, combined with a ServicePartitionResolver configured with your cluster location as a workaround. Using WCF will allow any client technology that understands SOAP or REST to connect to your service. Here's a sample implementation for a WCF service in ASF. This blog post describes how to use the resolver. 来源： https://stackoverflow

问题 I have a question regarding Service Fabric and Traefik. I have managed to succesfully deploy the Traefik application to a local cluster (and actually out in my own Azure Infra too). This is alongside a service (MyService) in another application I am trying to have Traefik (RP) sit in front of. I can see the Traefik dashboard, and I can see a backend (seemingly indicating that it has succesfully called the SF management API correctly for my application and service). I can also see an

问题 I m getting the following error on my local service fabric cluster node: Error event: SourceId='System.Hosting', Property='Activation:1.0'. There was an error during activation.Failed to setup ApplicationPrincipals. Error:ApplicationPrincipalAbortableError There is no much logs other than that, I m running VS2017 on Windows 10 with service fabric tools version: 3.0.480.9494 service fabric runtime version: 6.1.480.9494 I executed the following for service fabric powershell scripts: Set

问题 The documentation of Service Fabric recommends service remoting, ICommunicationClient or WcfCommunicationClient to realize the communication between the micro services. The ServiceBus, which I always used for inter-service communication, is not even mentioned. Why? 回答1: I think you misinterpreted the docs. It does not recommend any protocol or service (the word is not even present on the page). What it does do is list the built-in communication options and appropriate situations of when to

问题 In order to test and evaluate SF for production use, I created one (single-machine) test cluster on a production machine with three nodes, which worked fine. However, I failed to create a multi-machine cluster with three nodes. I followed these instructions: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-cluster-creation-for-windows-server/ All machines: are on the same (secure) network with the following IPs: 10.0.10.12, 10.0.11.12, 10.0.12.12. are virtual and were

问题 I have a ServiceFabric service hosting WebAPI. On a controller, I receive, in my Request, a FileStream . I have no problem reading the FileStream there. Then, I want this WebAPI service to call another SF service (stateful) - let's call it Service2, giving a MemoryStream in parameter. try { await _service2Proxy.MyService2Method(myMemoryStream, otherParameters); // Line after } catch { // Error handling } And in the Service2 public Task MyService2Method(MemoryStream ms, string otherParam) { //

问题 When using the Azure Service Fabric Reliable Actor programming model, what are the pros and cons of using several actor types in the same service? Is it only a matter of deployment, or are there runtime considerations as well? 回答1: Pros: Increases density. Fewer projects to manage which is always helpful. Cons: The actor types within the same package will have to be deployed/upgraded at the same time and are no longer independent. My advice would be to use the same code packages if the

问题 I've a docker image wiremock.net-nano which accepts additional commandline parameters like --Port and --AdminUsername . The normal docker commandline looks like: docker run --rm -p 9091:80 sheyenrath/wiremock.net-nano --ReadStaticMappings true --AdminUsername x --AdminPassword y --RequestLogExpirationDuration 24 But how can I configure these parameters in Azure Service Fabric ? The ServiceManifest.xml file defines only the image name ( <ImageName>sheyenrath/wiremock.net-nano</ImageName> ) and

问题 In the pre-GA version of Service Fabric I was registering a custom serializer like this: protected override IReliableStateManager CreateReliableStateManager() { IReliableStateManager result = new ReliableStateManager( new ReliableStateManagerConfiguration( onInitializeStateSerializersEvent: InitializeStateSerializers)); return result; } private Task InitializeStateSerializers() { StateManager.TryAddStateSerializer(new KFOBinarySerializer()); return Task.FromResult(false); } However, the