> Documentation says > > configtimeout > > How long the client should wait for the configuration to be retrieved before > considering it a failure. This setting is deprecated and has been replaced > by http_connect_timeout and http_read_timeout. This setting can be a time > interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or > years (5y). > > Default: 2m > > I'll try tweaking http_read_timeout.
The other side of this coin is, improve the time it takes to return the answer :-). I presume you are using PuppetDB for this? Perhaps some performance improvements can be made on that end of the stack. Have you looked into why the queries are taking so long to return yet? ken. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNT%3DySMR64Xctos6iWhESVGE_b2z-aBuBt%3DiZZskWL9%2BqAw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
