On Mar 10, 2:49 am, James Turnbull <[email protected]> wrote:
>
> Puppet 0.24.8 Release Candidate 1 is now available for testing.
Cool! It's now running on both of our puppetmasters and seems to be
working well.
The RPM spec file requires ruby-augeas. It would be nice if there
were
optional by having something like the following in the spec so
'rpmbuild -ba --without augeas' works:
%define with_augeas %{?_without_augeas: 0} %{?!_without_augeas: 1}
%if %{with_augeas}
Requires: ruby-augeas
%endif
> Enhancements to file serving, module and stored configuration
> performance
Even with these changes we can't run storeconfigs. It makes mysqld
eat all
of our CPUs and cry for more. We even stoppet puppetmaster, dropped
all of
the tables to remove any cruft, and restarted puppetmaster.
Is there some MySQL tuning we should do? FWIW, we turned on query
logging
and saw that one host generated 17k lines of query log output. That
seems
like a lot but what do I know? :) IIUC, every resource on every client
gets
an entry in the database. We have about 400 hosts and our stats
(based on
Puppet reports) say that we have 1.5 million total resources. Puppet
checks in once an hour so we have 1.5 million updates an hour.
How about giving storeconfigs some options to help improve
performance?
We'd be happy if all it gave us were fact names and values for each
host.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
