Saturday, June 14, 2025
1 change · 18.0
Resolved issues and error corrections
If a replica database connection fails, workers now periodically try to reconnect instead of staying on the primary database until they are recycled. This helps restore normal database load distribution within about 20 minutes after a temporary replica issue, reducing prolonged performance degradation.
Original PR description
When the connection to the replica database fails, the worker failover to the primary database and keeps on connecting to the primary database until the worker is recycled. This makes any hicups to the replica connection degrades the system for a very long time, as workers are only recycled once/twice a week. In this work, we makes so it attempts to reconnect to the replica database once every 20 minutes. This makes to the system recovers more quickly. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr