We faced similar issue. We now in process of switching to Puppet 4. Why not Puppet 5. Well it happened that latest 2.x PuppetDB works only with Puppet 4 so we must to do this intermediate step. Anyway I hoped that our standard server could handle at lest as twice as more agents as before, with passnger/httpd stack, but I was wrong. For now we have only 286 nodes connected to server with 40 cores E5-2680 v2 @ 2.80GHz and 384Gb RAM. Memory is not an issues but CPU is. PuppetDB with PostgreSQL on the same node. With this 286 nodes LA ~ 30. A lot of errors line JRuby timeout during instance borrowing with a 503/504 codes. Catalog compile time ca be 1000s or even more.
We use puppetserver 2.7 and agent 4.10.4 max-active-instances: 32 Also we use environment_timeout = unlimited with cache flusing. We used it on passenger and it gave us a huge performance boost. Maybe some here knows a way to optimize new puppetserver against CPU? Anyone changed borrow-timeout, environment-class-cache-enabled or compile-mode ? On Tuesday, October 3, 2017 at 3:11:32 PM UTC+3, Poil wrote: > > Hi, > > We have PuppetServer 2.8 on RHEL7. > > After some days computation of the catalog become slower and slower; the > load average of the compute nodes increased and the compute goes in > timeout. > > All our 4 computes nodes have 48 cores, only 10% of each core is used > when the timeout occured. > > We are on hiera v3, we only tuned "max-requests-per-instance: 5000" > because of a databases connection leak with our Trocla library. > > Only 150 nodes are connected to our PuppetServer. > > We never had this problem with Puppet3 (with more than 3000 nodes) > > Anyone have already see this or have a tips to resolv this ? > > Best regards, > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7b0ead25-e0f2-4f16-8c0e-9ef6c6387b9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
