[BUG] - Local/Dev cluster - Application is installed but no debug possible to due "System.FM Error" "Partition is below target replica or instance count" #1522
Labels
type-code-defect
Something isn't working
Describe the bug
Detailed description of the problem:
Application is installed but no debug possible to due "Partition below target replica".
Troubleshooting already performed: (for application failures, details from application logs investigation and why you think it is not application issue and SF issue)
Tried all mitigations from;
Stateless Service failed to start in Local Cluster - Microsoft Q&A and
"Partition is below target replica or instance count" error after deploying service fabric application to public service fabric cluster - Stack Overflow
Also tried resetting cluster.
Also, tried rebooting devbox.
Increasing disk space from 10GB to 30 GB, but still same behaviour:
After all mitigations and cluster resets also its same error.
Using a 5 node local-cluster
Attached ApplicationManifestxml and Local.5node.xml
Timestamp of problem start in UTC and duration:
24-01-2025
What entities (apps, services, partitions, replicas, nodes) are relevant?
fabric:/TrafficAnalyticsService
all partitions
Expectation from this ICM: (if this is for RCA. Please mark incident as mitigated)
SF team to help root cause this and mitigate this local issue as I am not able to resolve this by available mitigations
Area/Component:
Local SF Cluster
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This should work fine, till last week it was working but now its consistently failing. Local AF app debugging should work properly.
Observed behavior:
Error state of all microservice instance of applicatio, shared scnreeshot above in description
Screenshots
shared aboce
Service Fabric Runtime Version:
Code Version - 10.1.2175.9590
Environment:
If this is a regression, which version did it regress from?
Additional context
Add any other context about the problem here.
Assignees: /cc @microsoft/service-fabric-triage
The text was updated successfully, but these errors were encountered: