https://pulp.plan.io/https://pulp.plan.io/favicon.ico2018-05-03T15:48:25ZPulpPulp - Issue #3656: "TaskLock matching query does not exist" in logs every few secondshttps://pulp.plan.io/issues/3656?journal_id=280242018-05-03T15:48:25Zbmbouterbmbouter@redhat.com
<ul></ul><p>I've observed this several times in my dev environment. It's happening right now actually. I observe this most commonly when I suspend and resume the vagrant vm I have. Since my VM is currently showing this here are some details about my system.</p>
<p>1. The resource manager is running. I verified via a `ps | grep resource_manager`<br>
2. There are 0 TaskLock records. in my database</p>
<p>^ should not exist. The TaskLock record is created when the resource_manager starts and since it's still running it should not have been deleted. I can see that the reason it got deleted is because Pulp thought the resource manager was missing. I know this because it says:</p>
<pre><code>May 03 13:08:04 pulp3.dev celery[21105]: [2018-05-03 13:08:04,453: ERROR/MainProcess] Worker 'resource_manager@pulp3.dev' has gone missing, removing from list of
</code></pre>
<p>^ message was emitted exactly when I reopened my laptop. So what I think is happening is:</p>
<p>1. System is normal<br>
2. suspend VM<br>
3. Wait longer than 30 seconds<br>
4. resume VM<br>
5. observe that Pulp observes the resource_manager is lost and deletes its TaskLock<br>
6. The resource_manager continues heartbeating<br>
7. The handling of each of those heartbeats can't find the record it wants to "update"</p>
<p>Maybe that update should be a get_or_create?<br>
<a class="user active" href="https://pulp.plan.io/users/349">dalley</a> what do you think?</p>
<p>Note that the RQ branch removes TaskLock entirely so maybe we just wait for that to merge and then close this?</p> Pulp - Issue #3656: "TaskLock matching query does not exist" in logs every few secondshttps://pulp.plan.io/issues/3656?journal_id=280352018-05-03T23:19:30Zdalleydalley@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 3 MVP</i> added</li></ul><p>@jsherrill, are you installing from source or from PyPI?</p>
<p>If it's a source install, we should go ahead and fix this now. If PyPI, I'm fine with waiting until RQ merges.</p> Pulp - Issue #3656: "TaskLock matching query does not exist" in logs every few secondshttps://pulp.plan.io/issues/3656?journal_id=280852018-05-08T14:41:25Zdalleydalley@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #3656: "TaskLock matching query does not exist" in logs every few secondshttps://pulp.plan.io/issues/3656?journal_id=281862018-05-14T20:01:46Zbmbouterbmbouter@redhat.com
<ul></ul><p>The problematic code was removed with the adoption of RQ. You won't see this issue anymore. Please reopen if you do.</p> Pulp - Issue #3656: "TaskLock matching query does not exist" in logs every few secondshttps://pulp.plan.io/issues/3656?journal_id=281872018-05-14T20:02:05Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - WORKSFORME</i></li></ul> Pulp - Issue #3656: "TaskLock matching query does not exist" in logs every few secondshttps://pulp.plan.io/issues/3656?journal_id=282302018-05-15T13:15:34Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>CLOSED - WORKSFORME</i> to <i>CLOSED - WONTFIX</i></li></ul><p>We removed the line that was causing this error with the adoption of RQ. We didn't fix it, so I'm saying WONTFIX</p> Pulp - Issue #3656: "TaskLock matching query does not exist" in logs every few secondshttps://pulp.plan.io/issues/3656?journal_id=378992019-04-15T20:11:31Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>