Hide Forgot
Description of problem: Database replication is failing for LVDC After upgrade from 3.2 to 4.2 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This was caused by a combination of factors. -The latency between the remote server running the replication worker and the global was about 40ms. -The replication was slow enough that in many cases, the time to replicate one batch of data would exceed the replication subprocess heartbeat timeout and the process was being killed. -https://bugzilla.redhat.com/show_bug.cgi?id=1404028 was causing an incredible backlog (taggings and events) during provisioning. As a fix for this issue we will look at the frequency the replication process heartbeats to avoid the second issue mentioned above.