title: celerybeat - multiple instances & monitoring
body: <p>I'm having application built using celery and recently we got a requirement to run certain tasks on schedule.</p>
  
  <p>I think celerybeat is perfect for this, but I got few questions:</p>
  
  <ol>
  <li>Is it possible to run multiple celerybeat instances, so that tasks are not duplicated?</li>
  <li>How to make sure that celerybeat is always up &amp; running? </li>
  </ol>
  
  <p>So far I read this:
  <a href="https://github.com/celery/celery/issues/251" rel="noreferrer">https://github.com/celery/celery/issues/251</a>
  and 
  <a href="https://github.com/ybrs/single-beat" rel="noreferrer">https://github.com/ybrs/single-beat</a></p>
  
  <p>It looks like a single instance of celerybeat should be running. </p>
  
  <p>I'm running application inside AWS elasticbeanstalk docker containers and celery workers are also docker containers (so it's quickly scaleable when needed). </p>
  
  <p>It would be best to have celerybeat run through supervisord along with celery workers, but it seems this is not proper way to do this.</p>
  
  <p>At the same time having that single instance of celerybeat would require manual provision/start and monitoring. </p>