I believe you'll get an assertion failure by setting it to zero. In a way you probably don't want it to be pinned to 1 node, because if it is removed from the cluster or goes down you'll lose the garbage collection. However we don't have a nice way today of splaying the interval or anything magical like that. Is having it run in multiple places causing you an issue today?
On Mon, Jan 14, 2013 at 8:40 PM, Chuck <cssc...@gmail.com> wrote: > I have multiple puppetdb severs pointed at the same database. > > Would setting gc-interval to 0 disable it on the extra puppetdb nodes? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/4DEyx0IXbLsJ. > 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. -- 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.
