Bug 670876 - Logging too much when cloning a repo
Summary: Logging too much when cloning a repo
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: z_other
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks: verified-to-close
TreeView+ depends on / blocked
 
Reported: 2011-01-19 15:28 UTC by John Matthews
Modified: 2011-08-16 12:20 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-08-16 12:06:44 UTC
Embargoed:

Attachments (Terms of Use)

Description John Matthews 2011-01-19 15:28:32 UTC 
I noticed when I cloned Fedora 14 testing that a single log statement took up 3.8 MB.  

To reproduce.
Sync a large repo
Clone it

Look at /var/log/pulp/pulp.log.***

When this bug is present, you will see one of the log files, probably /var/log/pulp/pulp.log.1 is a few MB and contains a single line with lots of text:

2011-01-19 10:16:20,548 [INFO][Thread-5] _clone() @ repo.py:236 - Creating repo [f14_testing] cloned from [SON([(u'use_symlinks', False),....... <contains for 3.8MB in my case>
Comment 1 John Matthews 2011-01-19 15:31:48 UTC 
Fixed so log is only the repo id

2011-01-19 10:29:03,838 [INFO][Thread-5] _clone() @ repo.py:236 - Creating repo [f14_testing] cloned from [f14_testing]


Commit:
http://git.fedorahosted.org/git/?p=pulp.git;a=commit;h=ba2e5427b54c40c7930fbb4bf4c8083e0cfa7135
Comment 2 Jay Dobies 2011-01-21 19:18:48 UTC 
Fixed in 0.130.
Comment 3 Preethi Thomas 2011-02-04 19:26:09 UTC 
verified
[root@preethi ~]# rpm -q pulp
pulp-0.0.134-1.fc14.noarch

from the pulp.log
2011-02-04 13:54:48,513 [INFO][Thread-21] _clone() @ repo.py:237 - Creating repo [rhel5-pulp] cloned from [rhel5-pulp]
Comment 4 Preethi Thomas 2011-08-16 12:06:44 UTC 
Closing with Community Release 15

pulp-0.0.223-4.
Comment 5 Preethi Thomas 2011-08-16 12:20:43 UTC 
Closing with Community Release 15

pulp-0.0.223-4.
Note You need to log in before you can comment on or make changes to this bug.