Bug 489958 - High CPU usage and slow puppet performance
Summary: High CPU usage and slow puppet performance
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: puppet
Version: el5
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: David Lutterkort
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-12 17:11 UTC by Barrow Kwan
Modified: 2013-04-30 23:40 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-06-08 13:31:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Barrow Kwan 2009-03-12 17:11:35 UTC
Description of problem:
High CPU usage and slow puppet performance with the following puppet configuration

        file { "/some/path":
                owner => "user1",
                group => "group1",
                ensure => directory,
                recurse => true
        } 

Puppet discussion in Google Group http://groups.google.com/group/puppet-users/browse_thread/thread/3348b01f1bbc00ab

according to the discussion, there is a patch on either 0.25 or 0.24.8 which will allow "checksum" option to get around this problem.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Todd Zullinger 2009-06-01 03:08:07 UTC
Perusing the list discussion and upstream ticket, can't this be mitigated somewhat using checksum => undef?  And even that is only relevant if you've set a default checksum for the File type, if I'm reading things correctly.

At the least, it's being fixed upstream and it not likely something we can sanely backport to 0.24.8 in our packages.  Is there any objection to closing this as UPSTREAM?

Comment 2 Barrow Kwan 2009-06-08 05:40:30 UTC
sure

Comment 3 Todd Zullinger 2009-06-08 13:31:04 UTC
Done.  Thanks for reporting this and following up upstream!


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