mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-09-21 13:51:26 +02:00
Code Issues Projects Releases Wiki Activity

DOC: intro: minor updates and fixes

Browse Source 
- temporarily remove reference to management.txt which doesn't exist yet
- minor update to the lb intro
- indicate that e-mails can be sent to notify about server state change
This commit is contained in:
Willy Tarreau 2015-08-27 14:44:43 +02:00
parent 99a36dddf5
commit eff04f48b4
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/intro.txt
View File

@ -78,10 +78,6 @@ to the mailing list whose responses are present in these documents.
ensure you're running with all known fixes how to update it, complements and ensure you're running with all known fixes how to update it, complements and
alternatives. alternatives.
- management.txt : it explains how to start haproxy, how to manage it at
runtime, how to manage it on multiple nodes, how to proceed with seamless
upgrades.
- configuration.txt : the reference manual details all configuration keywords - configuration.txt : the reference manual details all configuration keywords
and their options. It is used when a configuration change is needed. and their options. It is used when a configuration change is needed.
@ -106,7 +102,7 @@ to the mailing list whose responses are present in these documents.
Load balancing consists in aggregating multiple components in order to achieve Load balancing consists in aggregating multiple components in order to achieve
a total processing capacity above each component's individual capacity, without a total processing capacity above each component's individual capacity, without
any intervention from the end user and in a scalable way. This results in more any intervention from the end user and in a scalable way. This results in more
operations being performed simultaneously by the time it takes component to operations being performed simultaneously by the time it takes a component to
perform only one. A single operation however will still be performed on a single perform only one. A single operation however will still be performed on a single
component at a time and will not get faster than without load balancing. It component at a time and will not get faster than without load balancing. It
always requires at least as many operations as available components and an always requires at least as many operations as available components and an
@ -139,7 +135,10 @@ A load balancer may act :
in deciding what server will process a connection or request. in deciding what server will process a connection or request.
Two distinct technologies exist and address different needs, though with some Two distinct technologies exist and address different needs, though with some
overlapping. overlapping. In each case it is important to keep in mind that load balancing
consists in diverting the traffic from its natural flow and that doing so always
requires a minimum of care to maintain the required level of consistency between
all routing decisions.
The first one acts at the packet level and processes packets more or less The first one acts at the packet level and processes packets more or less
individually. There is a 1-to-1 relation between input and output packets, so individually. There is a 1-to-1 relation between input and output packets, so
@ -592,7 +591,8 @@ and about reporting its own state to other network components :
SSL hello, LDAP, SQL, Redis, send/expect scripts, all with/without SSL; SSL hello, LDAP, SQL, Redis, send/expect scripts, all with/without SSL;
- State change is notified in the logs and stats page with the failure reason - State change is notified in the logs and stats page with the failure reason
(eg: the HTTP response received at the moment the failure was detected); (eg: the HTTP response received at the moment the failure was detected). An
e-mail can also be sent to a configurable address upon such a change ;
- Server state is also reported on the stats interface and can be used to take - Server state is also reported on the stats interface and can be used to take
routing decisions so that traffic may be sent to different farms depending routing decisions so that traffic may be sent to different farms depending