https://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-02-10T16:43:27ZPulpPulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=179332017-02-10T16:43:27Zbizhangbizhang@redhat.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Sprint/Milestone</strong> set to <i>33</i></li><li><strong>Severity</strong> changed from <i>2. Medium</i> to <i>3. High</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=179352017-02-10T16:44:03Zbizhangbizhang@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=181542017-02-22T15:49:14Zbizhangbizhang@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=181552017-02-22T15:49:21Zbizhangbizhang@redhat.com
<ul><li><strong>Assignee</strong> set to <i>bizhang</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=182602017-02-27T14:55:36Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>33</i> to <i>34</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=184422017-03-10T16:27:38Zbmbouterbmbouter@redhat.com
<ul></ul><p>Since we're moving away from Celery3.1 and into Celery4.0 I think we should defer this task. There are several bugs filed (maybe 4+) around memory leaks, cpu high usage, and file descriptor leaks against the Pulp workers. We should take all of them, and make one big testing story to evaluate correctness in all of those aspects with Celery4.0 and qpidd. I think that work would make the most sense as part of Pulp3 (as in add the pulp3 tag).</p> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=184902017-03-13T15:41:23Zbizhangbizhang@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-9 priority-6 priority-default closed" href="/issues/2632">Story #2632</a>: As a developer I want to reevaluate worker issues to see if they have been resolved by moving from Celery3 to Celery4</i> added</li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=185012017-03-13T17:28:14Zbizhangbizhang@redhat.com
<ul></ul><p>I just retested with the rawhide packages and the file descriptor leak was not present</p>
<pre><code>[root@dev ~]# for i in 18676 18682 18725 18729; do lsof -p $i | sort > lsof.${i}.1; done
[root@dev ~]# for i in $(seq 1 10); do service qpidd restart; sleep 15; done
[root@dev ~]# for i in 18676 18682 18725 18729; do lsof -p $i | sort > lsof.${i}.2; done
[root@dev ~]# wc lsof.*
173 1557 17742 lsof.18676.1
173 1557 17742 lsof.18676.2
173 1557 17742 lsof.18682.1
173 1557 17742 lsof.18682.2
173 1557 17742 lsof.18725.1
173 1557 17742 lsof.18725.2
173 1557 17742 lsof.18729.1
173 1557 17742 lsof.18729.2
</code></pre>
<pre><code>python2-celery.noarch 4.0.2-2.fc26 @rawhide
python2-kombu.noarch 1:4.0.2-4.fc26 @rawhide
python-qpid.noarch 1.35.0-3.fc26 @rawhide
</code></pre> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=185052017-03-13T19:41:28Zbizhangbizhang@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>CLOSED - WORKSFORME</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=185432017-03-16T14:46:14Zbizhangbizhang@redhat.com
<ul><li><strong>Status</strong> changed from <i>CLOSED - WORKSFORME</i> to <i>NEW</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=186312017-03-21T13:20:46Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Assignee</strong> deleted (<del><i>bizhang</i></del>)</li><li><strong>Sprint/Milestone</strong> deleted (<del><i>34</i></del>)</li></ul><p>We decided to wait on this issue, and let the upgrade to celery 4 fix it for us. We will try to reproduce on the new celery 4 stack, but expect it to be resolved.</p>
<p>See story <a href="https://pulp.plan.io/issues/2632" class="external">https://pulp.plan.io/issues/2632</a></p> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=347232019-03-12T17:43:39Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Issue #2582: Pipe leak in any parent Pulp celery process triggered by qpidd restarthttps://pulp.plan.io/issues/2582?journal_id=384292019-04-15T20:21:00Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>