Greg spotted this thread yesterday, interesting to read that people are
hitting problems with high numbers of facts.
I know we fixed a couple of things in 1.2 for minimising the database
load of importing facts, but it does lend credence to the idea of adding
a queue in future versions.
Dom
···
-------- Original Message --------
Subject: [Puppet Users] Disable certain facter facts?
Date: Mon, 24 Jun 2013 09:59:30 -0700 (PDT)
From: Roger
Reply-To: puppet-users@googlegroups.com
To: puppet-users@googlegroups.com
We found out, the hard way, that version 1.7 of Facter adds facts for
mounted linux file systems.
This is nice for normal servers. For a server hosting Oracle not so
good. We went from about 100 facts per server to well over 3,000 (our
Oracle boxes have quite a few volumes mounted).
Of course, this choked our ENC (Foreman) having this many facts pumped
into it and required us to downgrade Facter to the 1.6 series.
Is it possible to tell facter to ignore certain facts? Couldn’t find a
config file for it and not sure how puppet tells it to gather facts.
Would be useful so we don’t have to remain at 1.6.
Thanks,
–
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
Dominic Cleal
Red Hat Engineering
> Greg spotted this thread yesterday, interesting to read that people are
> hitting problems with high numbers of facts.
>
> I know we fixed a couple of things in 1.2 for minimising the database
> load of importing facts, but it does lend credence to the idea of adding
> a queue in future versions.
>
The only drawback in a queue for fact imports, is that potentially ENC
(param classes) might use a fact value to make a decision.
Maybe we could figure out if we actually have such params, and in cases
that we don't have send it to a queue?
I'm pretty sure that with large amount of facts per node the code we had
before 1.2 would not scale, I hope this one is much more robust.
Ohad
···
On Wed, Jun 26, 2013 at 10:45 AM, Dominic Cleal wrote:
Dom
-------- Original Message --------
Subject: [Puppet Users] Disable certain facter facts?
Date: Mon, 24 Jun 2013 09:59:30 -0700 (PDT)
From: Roger rojspencer@gmail.com
Reply-To: puppet-users@googlegroups.com
To: puppet-users@googlegroups.com
We found out, the hard way, that version 1.7 of Facter adds facts for
mounted linux file systems.
This is nice for normal servers. For a server hosting Oracle not so
good. We went from about 100 facts per server to well over 3,000 (our
Oracle boxes have quite a few volumes mounted).
Of course, this choked our ENC (Foreman) having this many facts pumped
into it and required us to downgrade Facter to the 1.6 series.
Is it possible to tell facter to ignore certain facts? Couldn’t find a
config file for it and not sure how puppet tells it to gather facts.
Would be useful so we don’t have to remain at 1.6.
Thanks,
–
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Do we know why such a serious performance degradation in Facter?
-d
···
On Wed, Jun 26, 2013 at 9:05 AM, Ohad Levy wrote:
On Wed, Jun 26, 2013 at 10:45 AM, Dominic Cleal dcleal@redhat.com wrote:
Greg spotted this thread yesterday, interesting to read that people are
hitting problems with high numbers of facts.
I know we fixed a couple of things in 1.2 for minimising the database
load of importing facts, but it does lend credence to the idea of adding
a queue in future versions.
The only drawback in a queue for fact imports, is that potentially ENC
(param classes) might use a fact value to make a decision.
Maybe we could figure out if we actually have such params, and in cases
that we don’t have send it to a queue?
I’m pretty sure that with large amount of facts per node the code we had
before 1.2 would not scale, I hope this one is much more robust.
Ohad
Dom
-------- Original Message --------
Subject: [Puppet Users] Disable certain facter facts?
Date: Mon, 24 Jun 2013 09:59:30 -0700 (PDT)
From: Roger rojspencer@gmail.com
Reply-To: puppet-users@googlegroups.com
To: puppet-users@googlegroups.com
We found out, the hard way, that version 1.7 of Facter adds facts for
mounted linux file systems.
This is nice for normal servers. For a server hosting Oracle not so
good. We went from about 100 facts per server to well over 3,000 (our
Oracle boxes have quite a few volumes mounted).
Of course, this choked our ENC (Foreman) having this many facts pumped
into it and required us to downgrade Facter to the 1.6 series.
Is it possible to tell facter to ignore certain facts? Couldn’t find a
config file for it and not sure how puppet tells it to gather facts.
Would be useful so we don’t have to remain at 1.6.
Thanks,
–
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
It's not Facter slowing down, it's Facter producing a huge number of
additional facts compared to previous versions. It now lists multiple
facts for each block device, with the size, vendor, model etc. On a
database or SAN-connected host, it's not too unusual to see hundreds or
thousands of such devices visible.
···
On 26/06/13 10:24, Dmitri Dolguikh wrote:
> Do we know why such a serious performance degradation in Facter?
> -d
–
Dominic Cleal
Red Hat Engineering
This is a one-time thing that occurs during the initial import (update) of
facts only?
-d
···
On Wed, Jun 26, 2013 at 10:36 AM, Dominic Cleal wrote:
On 26/06/13 10:24, Dmitri Dolguikh wrote:
Do we know why such a serious performance degradation in Facter?
-d
It’s not Facter slowing down, it’s Facter producing a huge number of
additional facts compared to previous versions. It now lists multiple
facts for each block device, with the size, vendor, model etc. On a
database or SAN-connected host, it’s not too unusual to see hundreds or
thousands of such devices visible.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Generally, yes, but also if any facts change. With block devices under
Linux, the device names aren't guaranteed to be static and will
generally flip around between boots, so fact names and values will
change a bit. But that's certainly a rare occurrence compared to every
Puppet run.
···
--
Dominic Cleal
Red Hat Engineering
On 26/06/13 10:50, Dmitri Dolguikh wrote:
This is a one-time thing that occurs during the initial import (update)
of facts only?
-d
On Wed, Jun 26, 2013 at 10:36 AM, Dominic Cleal <dcleal@redhat.com > mailto:dcleal@redhat.com> wrote:
On 26/06/13 10:24, Dmitri Dolguikh wrote:
> Do we know why such a serious performance degradation in Facter?
> -d
It's not Facter slowing down, it's Facter producing a huge number of
additional facts compared to previous versions. It now lists multiple
facts for each block device, with the size, vendor, model etc. On a
database or SAN-connected host, it's not too unusual to see hundreds or
thousands of such devices visible.
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
