Hi All,
I did an strace on the puppet client strace puppet agent --test --noop
and found out that it does an lstat and open. something like this
lstat("/opt/swapfiles/GQ/example1", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
open("/opt/swapfiles/GQ/example1", O_RDONLY|O_NONBLOCK|O_DIRECTORY) 7.
The swapfiles is a large directory with lots of files. Is there a way
to avoid this, since its taking lots of time to compile the catalog
from the puppetmaster. Can i somehow prevent this?
Regards,
Kevin
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> The swapfiles is a large directory with lots of files. Is there a way > to avoid this, since its taking lots of time to compile the catalog > from the puppetmaster. Can i somehow prevent this?I guess it''s not during compilation, as this happens on the master, rather while applying the catalog. How does your catalog looks like regarding that directory? Any recursive management? ~pete -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Jul 25, 9:06 am, Peter Meier <peter.me...@immerda.ch> wrote:> > The swapfiles is a large directory with lots of files. Is there a way > > to avoid this, since its taking lots of time to compile the catalog > > from the puppetmaster. Can i somehow prevent this? > > I guess it''s not during compilation, as this happens on the master, > rather while applying the catalog.No, he said he traced "puppet agent" on the client, so that''s where all the lstat()ing is happening. I suspect he wrote "compile" where he meant "apply". With that being the case, it looks and sounds like the usual issue with recursively managing a large directory. The usual response is something along these lines: 1) Avoid using puppet to recursively manage large directories or to manage large files 2) The best alternative is often to package the files for your system''s packaging system, and manage the package instead 3) If you *must* manage the file(s) themselves via Puppet then switch from MD5 checksumming to something cheaper, such as mtime checking (checksum => ''mtime''). John -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.