Story #1060

Updated by mhrivnak about 9 years ago

pulp_celerybeat currently can only be run in one process per deployment, once, and it is one of the single points point of failure in Pulp. Multiple instances of pulp_celerybeat should be able to be run concurrently. concurrently without failure. 


 1) Modify Pulp to be able to run multiple pulp_celerybeat process concurrently 
 2) Ensure that Pulp scheduled calls occur only once as expected even with multiple pulp_celerybeat processes running 
 3) Ensure that even if pulp_celerybeat processes start being killed, killed that scheduled calls still dispatch once and only once. 
 4) Document Documentation changes 
 5) Add Adding a release note 
 6) Verify Verification that the failure watcher code is safe to run concurrently 
 7) Verify Verification that the EventMonitor code is safe to run concurrently 
 8) Verify Verification that the WorkerTimeoutMonitor code is safe to run concurrently