- From: Jeff Blaine <
>
- To:
- Subject: [chef] Re: Re: Re: Intermittent failures with server 12.0.8?
- Date: Mon, 01 Jun 2015 10:50:37 -0400
>
The most likely cause of intermittent 401s are database timeouts
>
talking to postgresql. The erchef logs would tell for sure
>
(/var/log/opscode/opscode-erchef/request.log.N where N is an integer).
>
Chef Server 12.1.0 should improve database performance significantly;
>
however, for 12.0.8, you may see improvement by turning on queueing of
>
sql requests so that they don't fail immediately when all connections
>
are in use:
>
>
opscode_erchef['db_pool_queue_max'] = 40
>
opscode_erchef['db_pooler_timeout'] = 2000
Thanks Steve. I've made the changes and will see how things work out.
The defaults I saw in place were db_pool_queue_max = 20 and
db_pooler_timeout = 0
What negative effect would there be to 40/2000 being a new Chef server
default going forward? Obviously it changes from a fail-now behavior to
a fail-in-2sec behavior, but I don't immediately (and ignorantly) see
how anyone would care about that.
>
We've seen this reduce intermittent 401s caused by database issues at
>
large customer sites. We also have a patch in the works to make these
>
type of errors return 503s rather than 401s.
Good to hear. The 401 code threw us off.
--
Jeff Blaine
kickflop.net
PGP/GnuPG Key ID: 0x0C8EDD02
- [chef] Re: Re: Re: Intermittent failures with server 12.0.8?, Jeff Blaine, 06/01/2015
Archive powered by MHonArc 2.6.16.