[
https://issues.apache.org/jira/browse/CLOUDSTACK-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sowmya Krishnan closed CLOUDSTACK-2997.
---------------------------------------
verified maxconnections with updateNetworkOffering and able to see updated
value after reboot router.
Updated values persist after network restart. Also verified for VPC offering.
> 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
> Fix For: 4.2.0
>
>
> 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
