> Well I currently have 7,000 nodes in my PuppetDB instance and 8 puppetdb
> servers in various geographic locations.   The garbage collect seems to be a
> pretty intensive operation on the Postgres DB server in the current design.

Thats a shame to hear. What's the impact for you? I see from your
screenshot its averaging 16 seconds, is that what you are seeing?

> We have also been having an issue that started at the beginning of 2013 that
> we have not been able to narrow down at this time (we were on puppetdb 1.0.1
> for a long time with no issues.   Updated to 1.0.5 last week with no
> improvement)

This issue, is it related to the gc problem or something else? Can you
elaborate?

> I was planning on having my puppet manifest, for the puppetdb servers, elect
> one or two master puppetdb servers by querying for active puppetdb servers.
> So I would be dynamically electing the master(s) based on an algorithm.

Sounds good to me. Do you want to raise a feature request for this?

http://projects.puppetlabs.com/projects/puppetdb

Just more or less cover what you've said about wanting to disable by
setting to zero. I've already more or less got a patch that can
disable it when zero (its really just a conditional clause in the
right place), but I haven't done any thorough testing or gotten review
on it yet.

ken.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to