On Thu, Jun 14, 2012 at 1:31 PM, Chris Price wrote:
> Hi Matt,
>
> I think it would be worth opening a ticket for this
> ( http://projects.puppetlabs.com/projects/puppet/issues/new ).
Hi Chris,
This is now #15086. Hopefully there's enough info on the ticket to reproduce.
The VM is 1.5GB in size
On Thu, Jun 14, 2012 at 1:31 PM, Chris Price wrote:
> Hi Matt,
>
> I think it would be worth opening a ticket for this
> ( http://projects.puppetlabs.com/projects/puppet/issues/new ). The fact
> that you are seeing it with both storeconfigs/mysql and puppetdb/postgres
> leads me to believe that t
Hi Matt,
I think it would be worth opening a ticket for this (
http://projects.puppetlabs.com/projects/puppet/issues/new ). The fact that
you are seeing it with both storeconfigs/mysql and puppetdb/postgres leads
me to believe that the issue is more likely in puppet core than in either
of the
So, continuing this saga, I decided yesterday to try and make use of
puppetdb as it's supposed to have performance improvements over and
above storeconfigs.
My first change was to move from a MySQL to PostgreSQL database behind
storeconfigs. That still showed the issues I'm seeing. With
PostgreS
On Wed, Jun 13, 2012 at 4:54 PM, Kinzel, David wrote:
> Are you perhaps running into a max db connection issue (this should be
> recorded in logs).
>
> We set something like wait_timeout=60 in our mysql my.cnf to kill "idle"
> connections that don't seem to get properly reused.
I don't think s
>On Wed, Jun 13, 2012 at 3:58 PM, Jared Ballou
> wrote:
>> 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 in
On Wed, Jun 13, 2012 at 3:58 PM, Jared Ballou wrote:
> 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 g
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 ma
On Wed, Jun 13, 2012 at 2:53 PM, Matthew Burgess
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 concur