Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 883612

Summary: Got a MemoryError during sync of some large repos
Product: [Retired] Pulp Reporter: Steven Roberts <strobert>
Component: user-experienceAssignee: Sayli Karmarkar <skarmark>
Status: CLOSED DUPLICATE QA Contact: Preethi Thomas <pthomas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0.6CC: cperry, jason.dobies, skarmark
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-07 21:24:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
last 400 lines of the pulp.log none

Description Steven Roberts 2012-12-05 01:02:21 UTC
Created attachment 657854 [details]
last 400 lines of the pulp.log

Description of problem:
While doing repo sync's of some fairly large RHN repos (32 and 64 bit rhel5 and 64bit rhel6) saw a MemoryError scroll by in pulp.log

Version-Release number of selected component (if applicable):
the current 2.0 beta 2.0.6-0.11.beta

How reproducible:
unknown.  would take a while to try and replicate

Steps to Reproduce:
1. Create the 3 repos
2. initial a sync on all 3.
3. restart httpd due to mongodb running out of disk space
4. wait for the error.
  
Actual results:
2012-12-04 16:39:53,197 pulp.server.dispatch.call:ERROR:                                      
Traceback (most recent call last):                                                            
  File "/usr/lib/python2.6/site-packages/pulp/server/dispatch/call.py", line 204, in serialize
    data[field] = pickle.dumps(getattr(self, field))                                          
  File "/usr/lib64/python2.6/pickle.py", line 1367, in dumps                                  
    return file.getvalue()                                                                    
MemoryError                                                                                   

Expected results:
no memory error

Additional info:
I'll attach the pulp log.

machine running is a VM (running under vmware) with 4 CPU's, 6GB RAM and at the time 5GB swap.  I have added another 5GB of swap since.

Comment 1 Steven Roberts 2012-12-06 02:17:59 UTC
FYI, this may be a dupe of bug 873313.  stumbled across that bug and the symptoms sound familiar.

Comment 2 Jay Dobies 2012-12-07 21:24:54 UTC
Going to call this a duplicate of the one you mentioned. If it continues to happen in a future beta, we can revisit.

*** This bug has been marked as a duplicate of bug 873313 ***