I ran into this issue when Active(Record|Model|Support) had a version higher than 3.0.11. I'm running RHEL6 x64 with Ruby 1.8.7 from RPM and MySQL gem 2.8.1 built from source, if that rings true for you. Which versions of the installed gems do you have? And if you run the puppet master as puppet master --no-daemonize -vd does it give any pertinent output for us to look at?
As for data reads/writes, every time a node checks in, if storedconfigs is on, it will update the facts and some other ancillary information in the database. I've got about 400 nodes in my setup and it's still not very demanding on MySQL even with quite a lot of data going in and out, so the stock config values should suffice while you spend time tracking down all the other issues with getting the environment stood up. Good luck! -Jared On 06/13/2012 10:28 AM, Matthew Burgess wrote: > On Wed, Jun 13, 2012 at 2:53 PM, Matthew Burgess > <matthew.2.burg...@googlemail.com> wrote: > >> As soon as I set storeconfigs to false, and restart httpd (puppet is >> being served behind mod_passenger), a puppet-load >> run with 100 concurrent clients works with 100% success. > > Sorry, this should read 20 concurrent clients. 100 concurrent clients > happens to work as well, but > that's way above the level of scaling we require at present. > > In addition, the tests were run after performing a 'puppetd --test' to > store the initial config > in the DB. With no manifests being applied, I'm not expecting any > further writes to the DB during > the test runs. Is that a reasonable assumption, and therefore is it > also reasonable to assume > that I should be focusing my efforts on mysql read optimisations/tuning? > > Regards, > > Matt. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
