Project

Profile

Help

Story #2525

Updated by bmbouter over 7 years ago

pulp_resource_manager and pulp_celerybeat both us hot-spare processes for high availability. Whenever a pulp_resource_manager or pulp_celerybeat instance attempts to acquire their respective locks but cannot, (it is a hot spare (could not require backup instance), when it does acquire the lock) and then becomes the primary (acquires the lock) lock it should log something like "failover occured: xxxxxx is now the primary" to explicitly notify the user that failover has occurred.    The current Current behavior logs is to simply log when a worker the workers go missing, missing and when a new ones comes online, and when the lock is acquired. come online.

Back