Issue #4914 has been updated by Charlie Sharpsteen. Keywords changed from mount provider flush to mount provider flush customer
---------------------------------------- Bug #4914: mount provider slows down linearly w/ number of mounts https://projects.puppetlabs.com/issues/4914#change-88755 * Author: eric sorenson * Status: Closed * Priority: High * Assignee: * Category: mount * Target version: 2.6.7 * Affected Puppet version: 0.25.5 * Keywords: mount provider flush customer * Branch: https://github.com/stschulte/puppet/commits/ticket/2.6.x/4914 ---------------------------------------- The mount type/provider doesn't maintain any state between invocations. It appears to call /sbin/mount for each mount resource and looks through its output to determin if the filesystem currently under question is already mounted. This doesn't scale well on systems with a large number of mounts (say, several hundred) which are all managed through puppet, because each invocation takes a few seconds to complete... It'd be better if some form of pre-fetching were used, similar to the yum provider, so puppet can just consult its in-memory list of mountpoints. An additional refinement would be to only flush after the last mount resource were evaluated as this can also be expensive to do. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
