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 explorer went red and there are no more replicas present under the partition. And showed the health status as Error. Showing the error "Partition is below target replica or instance count".
Also I used the allowed port for creating the OWIN web server.
This doesn't happen when i deploy the application in local cluster. Service Fabric Explorer Screenshot for public cluster , Service Fabric Explorer Screenshot for Local Cluster
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.
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
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
I am using Azure Service Fabric to deploy my application and got this error.
After investigation, I found that it was because "TargetReplicaSetSize" and "MinReplicaSetSize" exceeded my node number.
To solve the problem, change "PartitionCount", "TargetReplicaSetSize" "MinReplicaSetSize" to 1 in ApplicationParameters/cloud.xml and re-deploy the application:
<?xml version="1.0" encoding="utf-8"?>
<Application xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Name="fabric:/Voting" xmlns="http://schemas.microsoft.com/2011/01/fabric">
<Parameters>
<Parameter Name="xxx_PartitionCount" Value="1" />
<Parameter Name="xxx_MinReplicaSetSize" Value="1" />
</Parameters>
</Application>
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.
来源：https://stackoverflow.com/questions/34892366/partition-is-below-target-replica-or-instance-count-error-after-deploying-serv