Story #2525
Updated by bmbouter over 7 years ago
h3. 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. h3. 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, lock) it should log the following: <code>Failover something like "failover occured: xxxxxx is now the primary</code> Additionally, the "lock acquired" log statement should be switched primary" to DEBUG since explicitly notify the WARNING statement will be shown to the user at that same moment. failover has occurred. The current behavior logs when a worker go missing, when a new ones comes online, and when the lock is acquired.
.