Closed PTC-JoshuaMatthews closed 4 years ago
Figured out what was going on
While I wasn't intentionally messing with the replicator endpoint, I was overriding some replicator setting with some code like
public MyStateFulService(StatefulServiceContext context) : base(context, new ReliableStateManager(context, new ReliableStateManagerConfiguration(new ReliableStateManagerReplicatorSettings { MaxReplicationMessageSize = 1073741824 }))){ }
Apparently this was overriding the default settings for the endpoint. I moved these settings to config and it seems to be working now.
I have a stateful service that can be deployed to my local 1 or 5 node cluster without error, but throws the following error when I deploy it to an Azure cluster
My replicator endpoint configuration is not modified from the default template.
The Secondary replicas are stuck InBuild, presumably because they are waiting for the primary to initiate the replication that it is failing to initiate.
Expected Behavior
All replicas should become ready as happens on my local cluster
Current Behavior
Secondary replicas are stuck InBuild, Primary replica cannot initiate replication.
Steps to Reproduce
1. 2. 3. 4.
Context (Environment)
Service Fabric Runtime and SDK Version :
7.0.470.9590
Operating System :
Windows server
Cluster Size : 5 node azure prod cluster
Possible Workaround
No