azure-service-fabric

问题 When I try to publish my Service Fabric application to a Azure cluster I get the following error message: 3>Copy-ServiceFabricApplicationPackage : Operation timed out. 3>At C:\Program Files\Microsoft SDKs\Service 3>Fabric\Tools\PSModule\ServiceFabricSDK\Publish-NewServiceFabricApplication.ps1:230 char:9 3>+ Copy-ServiceFabricApplicationPackage -ApplicationPackagePath ... 3>+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3> + CategoryInfo : OperationTimeout: (:) [Copy

问题 I have a service fabric cluster hosting legacy WCF services. Each of the WCF services is allocated a port number and uses the net.tcp protocol. I wonder what is the best way for service discovery and auto-scaling? I tried service fabric's DNS service and let service fabric assigns the port number for each service, however, the client won't know about the dynamic port number. The DNS service can only resolve the ip-address based on service DNS name. Since each service is on a specific port, I

问题 I'm wondering whether there is anything stored/managed in Service Fabric for a non-activated actor without persistent state? Let's say that an actor instance has the following life cycle: Actor is activated for the first time. Actor save state (persistent and replicated). Actor remove all saved state. Actor is deactivated (GC). Is there anything left now? Is it like we would have deleted it instead? 回答1: If you call IActorService.GetActorsAsync you will still get that actor in the list, so

问题 I'm wondering whether there is anything stored/managed in Service Fabric for a non-activated actor without persistent state? Let's say that an actor instance has the following life cycle: Actor is activated for the first time. Actor save state (persistent and replicated). Actor remove all saved state. Actor is deactivated (GC). Is there anything left now? Is it like we would have deleted it instead? 回答1: If you call IActorService.GetActorsAsync you will still get that actor in the list, so

问题 Please let me know whether service fabric supports capability similar to WoW64 ? I have a 32 bit .NET application which depends on 32 bit unmanged c++ dlls. Is it possible to run this application in Service Fabric in any way? 回答1: You can host any existing applications in Service Fabric (https://azure.microsoft.com/en-us/documentation/articles/service-fabric-deploy-existing-app/). However if you want to use reliable collections, reliable actors APIs, your application needs to be 64 bit. For

问题 I have a scenario where we need to store x*100 GBs of data. The data is in-general a good candidate for persistent state for an actor (well-partitioned, used by the specific actors only) in the service fabric cluster itself. Is the service fabric persistent state storage recommended for data of this scale? (Our compute load is going to be fairly low, so bumping up VMs just to store the state is not a desirable option.) How does the amount of persistent state affect the latency of moving

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

问题 In my Stateful service, I can write to the ServiceEventSource by calling this: ServiceEventSource.Current.ServiceMessage(this.Context, "this is my log message"); Does anyone know how I can make that same call in my Stateless WebAPI controller? It seems like I'm unable to get the context into the controller. I noticed it's only available in my OwinCommunicationListener . Basically, I want to be able to log my controllers like this: public async Task<IHttpActionResult> Get(string id) {

问题 I provisioned an Azure Service Fabric cluster in North Central US. I was able to initially publish my Service Fabric application to the cluster using Visual Studio and everything was running fine. I am now trying to upgrade the application via another Visual Studio publish, but the publish upgrade always fails with an Operation Timed Out error. Alternatively, I tried to just connect to the Service Fabric cluster using Powershell. I can't seem to do that either as I get the following failure

问题 I am trying to deploy a console application to service fabric. I was able to successfully deploy and run the application in local service fabric cluster. But when I am trying with public service fabric cluster, I am seeing below warning in service fabric explorer and the application is not running. Unhealthy event: SourceId='System.Hosting', Property='CodePackageActivation:C:EntryPoint', HealthState='Warning', ConsiderWarningAsError=false.There was an error during CodePackage activation.The