RepoMirrors/haproxy
1
0
Fork 0
mirror of http://git.haproxy.org/git/haproxy.git/ synced 2025-01-03 02:32:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

DOC: peers: Peers protocol documentation update.

Browse Source 
Add information about new peers protocol heartbeat feature.
This commit is contained in:
Frdric Lcaille 2019-03-26 16:17:33 +01:00 committed by Willy Tarreau
parent e88b77351b
commit cce34f8b4c
1 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/peers.txt
View File

@ -227,9 +227,10 @@
*** Control message class *** *** Control message class ***
At this time of writing, control messages are fixed-length messages used At this time of writing, control messages are fixed-length messages used
only to control the synchonrizations between local and/or remote processes. only to control the synchronizations between local and/or remote processes
and to emit heartbeat messages.
There exist four types of such control messages: There exists five types of such control messages:
+------------+--------------------------------------------------------+ +------------+--------------------------------------------------------+
| type byte | signification | | type byte | signification |
@ -248,7 +249,17 @@
| 3 | synchronization confirmed: acknowledge a finished or | | 3 | synchronization confirmed: acknowledge a finished or |
| | partial synchronization message. | | | partial synchronization message. |
+------------+--------------------------------------------------------+ +------------+--------------------------------------------------------+
| 4 | Heartbeat message. |
+------------+--------------------------------------------------------+
About hearbeat messages: a peer sends heartbeat messages to peers it is
connected to after periods of 3s of inactivity (i.e. when there is no
stick-table to synchronize for 3s). After a successful peer protocol
handshake between two peers, if one of them does not send any other peer
protocol messages (i.e. no heartbeat and no stick-table update messages)
during a 5s period, it is considered as no more alive by its remote peer
which closes the session and then tries to reconnect to the peer which
has just disappeared.
*** Error message class *** *** Error message class ***