On Fri, Jan 5, 2018 at 12:31 PM, John Sellens wrote:
> Hi Josh - thanks for the info.
>
> Can I make an assertion that having the default read timeout be unlimited
> is a mistake? In practical terms, anything over 60 seconds means
> something is broken.
>
Timeouts are
Hi Josh - thanks for the info.
Can I make an assertion that having the default read timeout be unlimited
is a mistake? In practical terms, anything over 60 seconds means
something is broken.
Could I suggest (without having to go and update the bug because I'm a
bad bad lazy person) that along
On Mon, Jan 1, 2018 at 10:08 PM, Matt Wise wrote:
> We're still tuning, but I ended up dropping our PuppetServer JRubyInstance
> count down to 2, and I have the -Xmx setting set to 4GB(!!). I think that
> we have a few libraries loaded in that are causing some major bloat,
We're still tuning, but I ended up dropping our PuppetServer JRubyInstance
count down to 2, and I have the -Xmx setting set to 4GB(!!). I think that
we have a few libraries loaded in that are causing some major bloat, but we
haven't had time to track that down yet.
The big concern I have is not
On Monday, January 1, 2018 at 5:52:10 PM UTC-5, Matt Wise wrote:
>
> *Puppet Agent: 5.3.2*
> *Puppet Server: 5.1.4 - Packaged in Docker, running on Amazon ECS*
>
I'm running a docker-compose based puppet setup, and had the same problem.
Short version was to increase the java heap size for the