Return
-
Title
Replication fails with "Replication session does not exist" -
Description
Replication fails with "Replication session does not exist."
Example stack trace:
System.InvalidOperationException: Replication session 'e91fd6d2-f6a7-4fee-9f9f-07b4d4c07859' does not existat Replay.Core.Implementation.Replication.Jobs.RemoteReplicationTransferJob.FindSessionOfCorrectType[T](Guid sessionId)at Replay.Core.Implementation.Replication.Jobs.RemoteReplicationTransferJob.TransferMissingRecords(Guid sessionId, Stream missingRawRecords)at Replay.Core.Implementation.Replication.RemoteReplicatedMasterAgent.TransferMissingRecords(Guid jobId, Guid sessionId, Stream missingRawRecords)at Replay.Core.Management.Replication.ReplicationCommunication.TransferMissingRecords(String agentId, String jobId, String sessionId, Stream missingRawRecords) -
Cause
This issue may occur when a replication jobs fails due to a network I/O error. The target core then closes the replication session and the session ID is removed. However, the source core continues to resume the replication session session with the removed session ID, resulting in the error. -
Resolution
There are two options to resolve:
- Remove the machine from replication on source and target cores, and then add it back to replication.
- Stop and start the core service on source and target cores.