mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-09-01 06:25:34 +00:00
Code Issues Releases Wiki Activity

[#999] Emphasize HA roles

Browse Source 
Applied the reviewer's patch which emphasizes important terms such as
primary, secondary, active etc.
This commit is contained in:
Marcin Siodelski
2020-05-08 11:18:24 +02:00
parent c32d564605
commit d8e2e72a9b
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/sphinx/arm/hooks-ha.rst
View File

@@ -61,7 +61,7 @@ can be switched to handle the entire DHCP traffic if its partner becomes
unavailable. unavailable.
In the load-balancing configuration, one of the servers must be In the load-balancing configuration, one of the servers must be
designated as "primary" and the other as "secondary." Functionally, designated as ``"primary"`` and the other as ``"secondary."`` Functionally,
there is no difference between the two during normal operation. This there is no difference between the two during normal operation. This
distinction is required when the two servers are started at (nearly) the distinction is required when the two servers are started at (nearly) the
same time and have to synchronize their lease databases. The primary same time and have to synchronize their lease databases. The primary
@@ -80,10 +80,10 @@ secondary server detects the failure of the primary, it starts
responding to all DHCP queries. responding to all DHCP queries.
In the configurations described above, the primary and secondary/standby In the configurations described above, the primary and secondary/standby
are referred to as "active" servers, because they receive lease are referred to as ``"active"`` servers, because they receive lease
updates and can automatically react to the partner's failures by updates and can automatically react to the partner's failures by
responding to the DHCP queries which would normally be handled by the responding to the DHCP queries which would normally be handled by the
partner. The HA hook library supports another server type/role: backup partner. The HA hook library supports another server type/role: ``"backup"``
server. The use of a backup server is optional, and can be implemented in both server. The use of a backup server is optional, and can be implemented in both
load-balancing and hot-standby setup, in addition to the active servers. load-balancing and hot-standby setup, in addition to the active servers.
There is no limit on the number of backup servers in the HA setup; There is no limit on the number of backup servers in the HA setup;