Issue #2906 has been updated by konrad rzentarzewski.
konrad rzentarzewski wrote:
> do you have a bandwidth and load measure for, say, fetching 100
> files/templates with and without keepalive? i believe ssl overhead will be
> significant for cpu when you deal with fair number of clients. and there is
> time penalty for clients (puppet runs) also, unless files are being fetched
> in parallel (and last time i've checked they were not).
btw. we workaround current affinity problems with following haproxy
configuration (maybe its worth to mention it in docs):
<blockquote>
global
quiet
nbproc 1
maxconn 64000
chroot /var/chroot/haproxy
user haproxy
group haproxy
daemon
stats socket /var/run/haproxy.socket user root group nagios mode 0660
log 127.0.0.1 local3 notice
listen puppet-proxy
bind :8140 # listen to TCP traffic on this port (SSL)
mode tcp
fullconn 1000
balance source
option ssl-hello-chk
server s1 10.100.101.14:8141 check
server s2 10.100.101.15:8141 check
</blockquote>
----------------------------------------
Feature #2906: keepalive support in puppetd
https://projects.puppetlabs.com/issues/2906
Author: konrad rzentarzewski
Status: Accepted
Priority: High
Assignee:
Category: fileserving
Target version: 2.7.0
Affected Puppet version: 0.25.1
Keywords:
Branch:
puppetd should keepalive 1 connection for all fileserver.* actions, and shedule
them at beginning, so that manifests are not applied if some of the actions
fail and puppetmaster load is less (1 connection per server per session).
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
