cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-2997) HAProxy maxconn is not configurable
Date Wed, 17 Jul 2013 04:54:48 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bharat Kumar resolved CLOUDSTACK-2997.
--------------------------------------

    Resolution: Fixed

dd33abffbe3b7c5b615e8f64b1824a720329dd0d
954e1978130b3cfb0c73f2f1506d94440f478f01
                
> HAProxy maxconn is not configurable
> -----------------------------------
>
>                 Key: CLOUDSTACK-2997
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2997
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.2.0
>         Environment: Master, Xen
>            Reporter: Parth Jagirdar
>            Assignee: Bharat Kumar
>            Priority: Critical
>
> In core//src/com/cloud/network/HAProxyConfigurator.java, maxconn is hardcoded to 4096.
According to the HAProxy page, it is safe to assume 20k connections per GB of RAM. This parameter
can be changed by the patches/systemvm/debian/config/root/reconfigLB.sh to be based on the
actual RAM of the VR.
> During testing following observations were made..
> - /etc/haproxy/haproxy.cfg doesnt have maxconn as global variable.
> - patches/systemvm/debian/config/root/reconfigLB.sh doesnt configure HAProxy.cfg as per
VR service offering and available RAM;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message