Actions
Story #2525
closed
Failover events should be explicitly logged as such when they occur
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
2.12.0
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Easy Fix, Pulp 2
Sprint:
Sprint 14
Quarter:
Description
Problem¶
pulp_resource_manager and pulp_celerybeat both use hot-spare processes for high availability. The current behavior logs when a worker go missing, when a new ones comes online, and when the lock is acquired.
Solution¶
Whenever a pulp_resource_manager or pulp_celerybeat instance is a hot spare (could not require the lock) and then becomes the primary (acquires the lock), logs should notify the user that failover has occurred. Specifically at WARNING level, it should log the following:
Failover occured: xxxxxx is now the primary
Additionally, the "lock acquired" log statement should be switched to DEBUG since the WARNING statement will be shown to the user at that same moment.
Actions
.
Explictly log failovers
Failover events are now logged as such at the WARNING level
closes #2525