Project

Profile

Help

Issue #970

Pulp freezes during association processing

Added by jluza over 6 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
2.7.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix, Pulp 2
Sprint:
Quarter:

Description

During tests of pulp-2.5 we often met situation when pulp froze in association process for even few minutes on one package. Solution was add sort index "_id" to _associated_units_by_type_cursor method, so pulp return always sorted data by one index. Patch applicable on master branch is included in files.

sort_id_in_assoc_query.patch (961 Bytes) sort_id_in_assoc_query.patch jluza, 05/11/2015 01:25 PM

Associated revisions

Revision b54816cf View on GitHub
Added by jluza over 6 years ago

sort with _id in every unit association query (prevents mongo from freeze)

This commit changes the unit association query's default sort to use the _id field instead of the unit key as it did before. Since the default sort is arbitrary, this improves performance while maintaining API compatibility.

https://pulp.plan.io/issues/970

fixes #970

Revision b54816cf View on GitHub
Added by jluza over 6 years ago

sort with _id in every unit association query (prevents mongo from freeze)

This commit changes the unit association query's default sort to use the _id field instead of the unit key as it did before. Since the default sort is arbitrary, this improves performance while maintaining API compatibility.

https://pulp.plan.io/issues/970

fixes #970

History

#1 Updated by bmbouter over 6 years ago

  • Subject changed from [RFE] fixed sort index in _associated_units_by_type_cursor to Pulp freezes during association processing

This looks like a bug report so I'm removing the [RFE] from the front. We don't use that syntax anymore. I also rewrote it some to match my understanding of the issue.

#2 Updated by jortel@redhat.com over 6 years ago

  • Priority changed from Normal to High
  • Triaged changed from No to Yes

#3 Updated by bcourt over 6 years ago

jluza, can you provide samples of the command line or rest API calls that you are making when you hit this issue? There are a lot of code paths that can hit this particular code. Thanks!

#4 Updated by rbarlow over 6 years ago

  • Status changed from NEW to POST
  • Assignee set to jluza
  • Platform Release set to 2.7.1
  • OS deleted (RHEL 6)
  • Tags Easy Fix added

#5 Updated by jluza about 6 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#6 Updated by amacdona@redhat.com almost 6 years ago

  • Platform Release changed from 2.7.1 to 2.7.2

#7 Updated by dkliban@redhat.com over 5 years ago

  • Status changed from MODIFIED to 5

#8 Updated by semyers over 5 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
  • Platform Release changed from 2.7.2 to 2.7.0

#9 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF