https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-06-16T21:46:24ZPulpPulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=50202015-06-16T21:46:24Zsbhawsinsbhawsin@redhat.com
<ul></ul><p>sbhawsin wrote:</p>
<blockquote>
<p>Celerybeat is one of the single point of failure in pulp. We should be able to make pulp highly available by making celerybeat highly available.</p>
<p>Deliverables:<br>
1) Able to run multiple celerybeat process<br>
2) By killing one of the process, pulp should not fail to work</p>
</blockquote>
<p>Design Doc: <a href="https://fedorahosted.org/pulp/wiki/PulpHACelerybeat" class="external">https://fedorahosted.org/pulp/wiki/PulpHACelerybeat</a></p> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=50322015-06-17T13:49:11Zbmbouterbmbouter@redhat.com
<ul><li><strong>Subject</strong> changed from <i>To be able to run pulp with multiple celeryBeat instances and make it HA</i> to <i>As a user I can run Pulp with multiple celeryBeat instances</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5032/diff?detail_id=4590">diff</a>)</li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=50332015-06-17T13:51:25Zbmbouterbmbouter@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5033/diff?detail_id=4591">diff</a>)</li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=50342015-06-17T13:51:37Zbmbouterbmbouter@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5034/diff?detail_id=4592">diff</a>)</li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=50352015-06-17T13:55:39Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/5035/diff?detail_id=4593">diff</a>)</li><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=50822015-06-22T12:14:32Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p><a href="https://github.com/pulp/pulp/pull/1940" class="external">https://github.com/pulp/pulp/pull/1940</a></p> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=53002015-07-06T16:48:25Zbmbouterbmbouter@redhat.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-1 status-11 priority-6 priority-default closed" href="/issues/1113">Issue #1113</a>: If an instance of pulp_celerybeat dies unexpectedly, Pulp incorrectly tries to "cancel all tasks in its queue"</i> added</li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=53092015-07-06T19:26:57Zsbhawsinsbhawsin@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Story 1060: Pulp with multiple celerybeat instances https://pulp/plan.io/issues/1060 closes #1060" href="https://pulp.plan.io/projects/pulp/repository/pulp/revisions/df6ad2850870dc7aac0fe1f6d754dbb0c57e3a20">pulp|df6ad2850870dc7aac0fe1f6d754dbb0c57e3a20</a>.</p> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=53332015-07-07T11:52:26Zbmbouterbmbouter@redhat.com
<ul></ul><p>QE, you should use a clustered setup to run pulp_celerybeat on two machines. Then configure some scheduled operations and ensure that the expected number of operations occur. If you kill -9 one of the pulp_celerybeat and leave the other running everything should still work including manual sync+publish operations, and scheduled operations. Note, a sync may take up to 270 seconds to failover after killing a pulp_celerybeat, but it is still expected to recover.</p> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=72302015-12-02T19:58:51Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Platform Release</strong> changed from <i>master</i> to <i>2.8.0</i></li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=92062016-02-23T20:55:26Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=100742016-03-23T18:15:12Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Story #1060: As a user I can run Pulp with multiple celeryBeat instanceshttps://pulp.plan.io/issues/1060?journal_id=397532019-04-15T20:47:14Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>