btzq opened a new issue, #9800:
URL: https://github.com/apache/cloudstack/issues/9800
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Virtual Router, HA Proxy
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.1
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
One of our customers required larger HA Proxy Max Connections as they have
many users connecting at the same time.
So, we change the default value of the below parameter in Global Settings to
a new one:
- network.loadbalancer.haproxy.max.conn = 500,000 (Previous is 4096, which
was the default value)
Once implemented, and we restarted the cloudstack server, we got a whole
bunch of healthcheck failures.
Screenshot below:
In this case, I dont think this should be counted as a healthcheck issue.
Because the service seems to be working fine.
I think what would be a better experience for the operator, is to mark the
router as 'Requires Upgrade'.
Because the VR does not need to be re-created. It just needed to be forced
rebooted. (FYI, normal reboot doesnt seem to cause the VR to load the new
maxconn value).
And as an operator, we rely on the 'Alert' section to ensure all customer VR
are working normally. This current behavior creates alot of noise.
Even better, is for each customer to be able set their own
(network.loadbalancer.haproxy.max.conn) value, and additional settings. Because
not all customers requires such large values.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
Refer above
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Mark the router as 'Requires Upgrade', when a Global Setting is changed,
such as network.loadbalancer.haproxy.max.conn
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Bombarded with Health Check fails for all VRs created, which requires manual
force reboot or cleanup VR. (normal reboot doesnt work).
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
