Hey Mike,
The unsatisfying answer is that PuppetDB handles giant facts
(particularly array-valued facts) pretty badly right now, and facter's
disks, partitions, and mountpoints facts can all get pretty huge in
cases such as SANs and similar. Can you try and see if the bulk of those
fact paths are coming from a small set of your nodes? I expect this
query might help:
https://gist.github.com/wkalt/4a58b9a97c79eee31971e5fc04dec0e4
You can mask the facts on a per-node basis by creating a custom fact
with value nil and weight 100 as described here:
https://docs.puppet.com/facter/3.1/custom_facts.html#fact-precedence
(this assumes you aren't using these facts for anything, but that sounds
like the case.)
Longer term, this is something we need to fix on our end. I created
https://tickets.puppetlabs.com/browse/PDB-2631 to track the issue.
https://tickets.puppetlabs.com/browse/FACT-1345 may also be related.
If you get those nodes tracked down, would you mind telling us the
operating system?
Wyatt
--
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/5716546A.9020400%40puppet.com.
For more options, visit https://groups.google.com/d/optout.
