“Partition is below target replica or instance count” error after deploying service fabric application to public service fabric cluster

Question

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

Answer 1

I just had the same error message. Turned out my container was not built yet. It took a few minutes but then the status changed to OK.

Answer 2

I got the same issue today and besides the possible reasons mentioned by other answers, another possible reason is you are using old versions for SF runtime/SDK/library.

Please make sure your SF runtime & SDK & referenced DLLs in your project are latest!

Answer 3

Most of the time this error really just means "we couldn't get your service started." If an unhandled exception in your service is preventing it from starting, you can drill down to your service instance or replica in the Service Fabric Explorer to see a stack trace when it fails to start after multiple attempts.

BTW, I would recommend using the newer web-based Service Fabric Explorer. Just point a web browser to port 19080 on your cluster: e.g., http://mycluster.eastus.cloudapp.azure.com:19080/Explorer/index.htm.

Answer 4

Just a little comment from my side..after spending hours on this error the problem was in a low disk space on my C:\ drive. After increasing the free space from around 3GB to 8GB the error disappeared.

As stated here: https://github.com/Azure/service-fabric-issues/issues/15

The default installation requires around 10Gb of disk space today

Answer 5

I came across this issue and it was a config error.

The error in service Fabric explorer on port 19080 said:

Error event: SourceId='System.FM', Property='State'.

Partition is below target replica or instance count. fabric:/MyApp/MyService 3 2 [partitionid] N/P RD _Node_0 Up [a long numeric] (Showing 1 out of 1 replicas. Total available replicas: 1.)

In my ApplicationManifest.xml I had :

  <Service Name="MyService">
  <StatefulService ServiceTypeName="MyServiceType" TargetReplicaSetSize=**"3"** MinReplicaSetSize=**"2"**>
    <SingletonPartition />
  </StatefulService>
</Service>

Reducing MinReplicaSetSize to 1 and TargetReplicaSetSize to 1 and republishing solved the problem on my end.

Classic Eye-Dee-Ten-Tee (ID10T) config issue :-D

Answer 6

Another reason is if you created a stateless service ( check ApplicationPackageRoot/ApplicationManifest.xml) but the service implements stateful service.