Hi,

> On 12 Dec 2017, at 12:41, n.bele...@gaijin.ru wrote:
> 
> Hello!
> 
> We have a problem with very slow work puppetserver.
> 
> 
> We have ~300 nodes, master runs on a server with 24 cores and 20 GB of memory.

Low number of nodes. Enough CPU and RAM.

> 
> Pappet agent log:
> 
> Notice: Applied catalog in 4845.82 seconds
> Changes:
>             Total: 1043

Many changes. Is this initial Puppet run or is this standard that you have 1043 
changes on every Puppet run?

> Events:
>           Success: 1043
>             Total: 1043
> Resources:
>       Out of sync: 1025
>           Changed: 1025
>             Total: 1521
>         Restarted: 38
> Time:
>        Filebucket: 0.00
>         Resources: 0.00
>    Sensu api config: 0.00
>    Sensu redis config: 0.00
>    Sensu enterprise dashboard config: 0.00
>       Concat file: 0.00
>          Schedule: 0.00
>    Sensu client config: 0.00
>            Anchor: 0.00
>    Concat fragment: 0.00
>         Mailalias: 0.00
>    Sensu rabbitmq config: 0.02
>         Ipmi user: 0.03
>             Group: 0.05
>              Cron: 0.07
>           Yumrepo: 0.07
>       Sensu check: 0.08
>              Host: 0.09
>              User: 0.97
>          Last run: 1513034474
>              Exec: 19.23
>            Sshkey: 2.83
>           Package: 232.51
>            Augeas: 5.00
>              File: 4466.81
>             Total: 4810.97

Which Puppetserver version are you running?
What are you doing with file resources?
Which packages do you manage?
In the timing list you see that file resource type and the package resource 
type take the most time.



>    Config retrieval: 75.19
>           Service: 8.01
> Version:
>            Config: 1513029567
>            Puppet: 4.4.1
> 
> 
> 
> In fact, time is even 1.5 times more.
> 
> strace master process (and his thread of course):
> # cat strace.txt | grep stat | wc -l
> 2094587
> # cat strace.txt | grep -v stat | wc -l
> 566745
> 
> There are a lot of call:
> 26104 stat ("/ etc / puppetlabs / code / environments / production / shared / 
> modules / elasticsearch / lib / puppet / parser / functions /../../../ hiera 
> / backend / eyaml / encryptors / pkcs7.rb" , <unfinished ...>
> Threads call it many of times and hang in this state. We use the elastic 
> module for a long time and there were no this problem.

That is OK. That is hiera eyaml called via lookup or automatic data binding.


> 
> How can I understand, what is the reason for this?
> 
> -- 
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/deefad16-f62e-4b3f-98f8-eedeeb12b30c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/93F7BDFF-4472-48A0-8316-49E60DBEE0C6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to