This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
With replication enabled, RecoveryManager spins uselessly on primary instead of waiting for events. #1537
Labels
performance
Performance related issues or changes.
Feature Request
Summary
With replication enabled, RecoveryManager spins uselessly on primary instead of waiting for events.
Solution
Look at
RecoveryManager::RunTask()
and get rid of the while loop hack.ReplicationLogProvider::WaitForEvent()
was added much later and might be helpful here if you can modify it accordingly.And/or, look at
AbstractLogProvider
.In general, the
RecoveryManager
needs to be able to distinguish between "this log provider will never get more logs" (wal.log) and "this log provider may get more logs" (replication).The text was updated successfully, but these errors were encountered: