I’m trying to understand how the distributed data replicator behave at start up time.
From what I have observed,
it seems the the replicator first tries to load everything stored in the local durable storage.
if there is any deserialization failure, the replicator crashes, or keep retrying.
the concequence is that the replicator does not participate in the ddata cluster and does not handle any commands.
Is my understanding correct?
Is there a way to configure ddata to ignore all the deserialization failures, after logging them?
2 posts - 2 participants