I use the write/read configuration built into PuppetDB and point the interfaces to VIPs behind a netscaler.. Netscaler load balances to the puppetDB instances and they're all setup so that writes happen to the primary DB node and reads can happen on the VIP for the slave nodes. The slave nodes just use log shipping in postgres 9.4.
I'm not running 8000 nodes, but we do have about 2k and i get away with running puppetdb in vmware on fairly small sized VMs. We use the crap out of read access for internal tooling and 30 minute checkins don't seem to cause much load for writes. -byron On Thursday, July 2, 2015 at 8:15:00 AM UTC-5, miguel wrote: > > On Thu, Jul 2, 2015 at 6:39 AM, Erik Dalén <erik.gus...@gmail.com > <javascript:>> wrote: > > > > We have separated the PuppetDB service hosts and the postgres databases > to > > different hosts. For postgres we have a write master with a hot standby > and > > four read-only slaves (one for each PuppetDB host). This was scaled up > when > > we actually had some performance issues with earlier PuppetDB versions > and > > can likely be scaled down to just two service hosts and read-only slaves > > without issues now. > > > > Could you share how did you configure the write-master and the read-only > slaves? > > Did you use the write/read separation of PuppetDB configuration? > -- 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/15f0cd84-bc4c-48cc-9c06-ab51fb7a3294%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
