Rethinking on this, the problem is that the LoopTuner timeout code does not kick in when the DBLoopTuner is blocking for replication lag. The loops should terminate after the abort time, even if it never got a chance to do anything due to lag or long running transactions.
Rethinking on this, the problem is that the LoopTuner timeout code does not kick in when the DBLoopTuner is blocking for replication lag. The loops should terminate after the abort time, even if it never got a chance to do anything due to lag or long running transactions.