Issue #13103 has been updated by Josh Cooper.
Affected Puppet version deleted (2.7.12rc2)
The puppet agent performs pluginsync within a `Timeout.timeout` block to ensure
the download doesn't take more than `Puppet[:configtimeout]` seconds. This ends
up creating a thread that simply sleeps for the desired timeout. When puppet is
executing code within the timeout block, the cpu utilization spikes.
I am able to reproduce the cpu spike simply by executing the following:
<pre>
Thread.new { sleep(10000) }
</pre>
I don't see the issue with ruby 1.9.3, so likely the answer to this, will be to
upgrade to ruby 1.9.
----------------------------------------
Bug #13103: CPU reached 100% during catalog run on puppet node
https://projects.puppetlabs.com/issues/13103#change-66169
Author: Collaboration TR
Status: Investigating
Priority: Normal
Assignee: Josh Cooper
Category: windows
Target version:
Affected Puppet version:
Keywords: windows, ftw
Branch:
After installing and ran command "puppet agent --test" on windows machine. I
observed CPU utilization from task manager and found that The CPU usage reached
100% while connecting to puppet master to poll the catalog and dropped down
when the catalog run is completed (about 10-30 seconds).
I use puppet agent windows preview version 2.5 which the official version will
be released this April.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
