Hi
The reason is we want to be 100% sure of the route the packet travelled
once through the initial HAproxy LB. This for troubleshooting but also
audit purposes.
On 27/04/2014 10:18, Markus Rietzler wrote:
Am 25.04.14 19:53, schrieb Kobus Bensch:
Hi Paul
We use haproxy to multiple https servers. After this we have a separate tomcat
server for each http server. So a one to one relationship between Apache and
tomcat. We then use apache to shop to the tomcat servers.
----------------------
| haproxy1 HA haproxy2 | using corosync/pacemaker
-----------------------
Apache1. Apache2
| |
Tomcat1 Tomcat2
\ /
\ /
MySQL DBS
Sent from my iPhone
On 25 Apr 2014, at 18:19, Paul Hirose <[email protected]> wrote:
I was wondering if anyone uses haproxy for http -> ajp (tomcat) load-balancing. I
often use haproxy for http -> http, but I was just wondering what would need to
happen for the incoming http(s) request to get translated into ajp and forwarded to
tomcat's ajp connector rather than the http connector.
If not, I suppose I could do the http -> ajp conversion in apache httpd, and
place haproxy in between the httpd process and multiple tomcat backends using tcp
mode rather than http mode.
I've no specific need for this yet, per se. Just curious.
Thanks,
PH
==
Paul Hirose
with ajp you can use loadbalancing in apache to use several backend tomcat
servers. it should work with haproxy but i
wonder why not use load balancing with apache. its there already...
markus
--
Trustpay Global Limited is an authorised Electronic Money Institution
regulated by the Financial Conduct Authority registration number 900043.
Company No 07427913 Registered in England and Wales with registered address
130 Wood Street, London, EC2V 6DL, United Kingdom.
For further details please visit our website at www.trustpayglobal.com.
The information in this email and any attachments are confidential and
remain the property of Trustpay Global Ltd unless agreed by contract. It is
intended solely for the person to whom or the entity to which it is
addressed. If you are not the intended recipient you may not use, disclose,
copy, distribute, print or rely on the content of this email or its
attachments. If this email has been received by you in error please advise
the sender and delete the email from your system. Trustpay Global Ltd does
not accept any liability for any personal view expressed in this message.
