This article describes an issue regarding replication failure due to a short timeout buffer (during all types of replication).
You may experience this issue during the following scenarios:
To resolve the issue it is necessary to increase the replay engine read and write timeout settings from 30 seconds to 5 minutes (this can be done from the Core Configuration tab). This will prevent the consume process from timing out. After performing this changes, please do the following steps:
1. Delete the server agent from within the Target core Replication tab.
2. Delete/Remove the outstanding seed on the source core from the Replication tab.
3. Delete the server agent on the source core Replication Tab.
4. Add the server agent back to Source Core Replication and perform seed drive replication again.
This may take a long time, but after its completion, the seeding process should run while the other tasks are running without little impact.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center