On Wednesday, November 5, 2014 9:47:02 AM UTC-5, jcbollinger wrote:
>
> On Tuesday, November 4, 2014 9:32:32 AM UTC-6, Georgi Todorov wrote:
>>
>> On Tuesday, November 4, 2014 9:50:15 AM UTC-5, jcbollinger wrote:
>>>
>>> By far the biggest difference is i
On Tuesday, November 4, 2014 9:50:15 AM UTC-5, jcbollinger wrote:
>
> By far the biggest difference is is File retrieval time. This will be for
> File resources where you specify content via a 'source' parameter rather
> than via a 'content' property. The agent must make a separate request to
On Friday, October 31, 2014 9:50:41 AM UTC-4, Georgi Todorov wrote:
>
> Actually, sometime last night something happened and puppet stopped
> processing requests altogether. Stopping and starting httpd fixed this, but
> this could be just some bug in one of the new versions o
On Thursday, October 30, 2014 11:56:14 PM UTC-4, Garrett Honeycutt wrote:
>
> Hi Georgi,
>
> The catalog compilation time is how long it takes to compile the catalog
> *on the master*. You can find it on CentOS with `grep Compile
> /var/log/messages`. The amount of time it takes for your agent
Chris, I sleep very well :). Our master is hourly backed up (the entire vm)
and all configs go though git. Redeploying/restoring the master should be
fairly quick (I have not tried though). Also, the way we use puppet, if it
is down, it is no harm really. Only needed to push changes, which we do
Hi group,
We have a VM with 24 E7-8857 v2 @ 3.00GHz cores and 32G of ram (on big ESX
hosts and fast backend) that is our foreman/puppetmaster with the following
tuning params:
Passanger:
PassengerMaxRequests 1
PassengerStatThrottleRate 180
PassengerMaxRequestQueueSize 300
Passenger
