azure-service-fabric

问题 I see advantages of Kubernetes which include Rolling Deployments, Automatic Health check monitoring, and swinging a new server to action when an existing one fails. I also do understand that Kubernetes is not just for Docker. So, that brings a couple of questions! When Azure, and Service Fabric could provide all that I said (and beyond), why would I need Kubernetes? Would it make sense for one to use Kubernetes along with Service Fabric for large scale deployments on Azure? 回答1: Let's look

问题 I have created a service fabric stateless reliable service, in which i used OWIN to host a web API. When I deployed the application to the Local cluster, it worked fine and i could call the API. When i deployed the application to the public cluster, The deployment completed successfully but when i inspected the cluster using Service fabric explorer, the the replicas seemed to be in "In Build" status for sometime, then it moved to "Warning" State and finally the entire tree in the fabric

问题 I have added a Stateless Service Fabric project to my solution and set it up as a Web Api self host. I have touched nothing in any of the files added by Visual Studio. The only thing that went slightly wrong was a Git merge error on the solution file, causing me to have to add the projects again manually. Projects are named as follows: Project name/sfproj: ClientCore.CommandStackApi.Deploy Service name/csproj: ClientCore.CommandStackApi When I try to deploy, I get the following error: The

问题 I found the following API await fabricClient.ClusterManager.ProvisionFabricAsync(null, "testMani.xml"); but have not figured out where to store the new manifest.xml file? using it as listed here it will throw exception that the file testMani.xml do not exist in the store. How can one after deployment manipulate the cluster manifest. 回答1: The cluster manifest and APIs that reference it are artifacts of Service Fabric's internal usage at Microsoft. Manipulating the manifest is not recommended

问题 How does Azure Reliable Dictionary actually handles data persistence. Is it like SQL which persists mostly all data excepts indexes(i.e. key in our case) on disk or is like hashmap which have everything in memory(i.e. both key and value) and just keeps a backup on disk 回答1: The current implementation of Reliable Collections store the entire set of data in the memory, and a copy serialized in the disk. It is required to stay in memory because the data stored in the disks are serialized and a

问题 I want to use an azure automation account to connect to a service fabric cluster and run a health check. I'm struggling with establishing a connection to the cluster because the service fabric sdk is not present. Is there a way to use the service fabric powershell cmdlets in an azure automation runbook? 回答1: You could import AzureRM.ServiceFabric 0.2.4 module to Azure automation account. Open the link https://www.powershellgallery.com/packages/AzureRM.ServiceFabric/0.2.4 and click Deploy to

问题 If I've understood the docs properly, azure service fabric-based apps/microservices cannot be installed together with their service-fabric operational environment in one "packaged installer" step. For example, if I want to deploy a set of microservices on premises at a company that is running a typical windows server 2012 or VMWare IT center, then I'm out of luck? I'd have to require the company to first commit to (and execute) an installation of an azure app service fabric on several

问题 Is there a way to increase number of instance for stateless service on Service Fabric please? We can update the application manifest to increase the number however that will require a deployment. Is there a way to do that via Service Fabric Explorer or Powershell please? Thank you very much Best regards 回答1: Yes using the Update-ServiceFabricService cmdlet Update-ServiceFabricService [-Stateless] [-ServiceName] <Uri> [-Correlation <String[]>] [-DefaultMoveCost <String>] [-Force] [

问题 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

问题 I've run out of storage on my Azure Service Fabric sclesets, so can no longer deploy any updates. I'm guessing this is because SF is keeping track of all the deployments and using up space. Can anyone tell me if there is: 1) A way to tell service fabric to delete old deployments (say older than 10 days ago.) 2) A way to increase the storage available on the scalesets (Service Fabric is currently using the OS disk for deployments) 回答1: Regarding your first question, There is no way to tell SF