You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Puppet Users
Hi there we have a puppetserver 6.4.0 which is currently handling about 450 clients. In terms of performance over our legacy 3.8 instance it is great - clearly clojure is faster than a rails app behind a web proxy :-) But we notice that when we hit approx. 90 established connection to TCP port 8140 any new client puppet-agent connections "hang" at this stage as seen from debug output:
This isn't just waiting for a catalog to compile - it often sits there for minutes with no response. In fact if we reboot the puppet server thus clearing the connections the client then runs normally as expected - with just a small delay waiting for its catalog.
I'm pretty sure this is not some OS / TCP stack limitation so wonder if there is some config which might be throttling this at the application level ? I hope approx. 450 clients is not the stage we need to start scaling to multiple catalog servers ??
Thanks for your help, Andy.
Ramin K
unread,
Oct 9, 2019, 6:28:54 PM10/9/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet...@googlegroups.com
I'd look at general tuning as a first step. From puppetserver.conf
450 servers every 30 minutes is 4s. If catalog compile is taking longer
than 4s a single core instance is likely falling behind. I believe
Puppet recommends 4 core minimum to handle OS, JVM, garbage collection,
etc. Distributing file resources through Puppet will take CPU time away
from catalog compiles. I'd only be concerned about 200-300 or so.