mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-31 14:05:33 +00:00
Code Issues Releases Wiki Activity

[#362,!182] Added clarification about Cassandra connection failure handling

Browse Source
This commit is contained in:
Tomek Mrugalski
2019-02-22 14:04:41 +01:00
parent 8176e6a7c3
commit d114f1d8ce
2 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/guide/dhcp4-srv.xml
View File

@@ -496,7 +496,9 @@ the lease database after connectivity has been lost may be specified:
If the server is unable to reconnect to the database after making the maximum number If the server is unable to reconnect to the database after making the maximum number
of attempts the server will exit. A value of zero (the default) disables automatic of attempts the server will exit. A value of zero (the default) disables automatic
recovery and the server will exit immediately upon detecting a loss of connectivity recovery and the server will exit immediately upon detecting a loss of connectivity
(MySQL and Postgres only). (MySQL and Postgres only). For Cassandra, Kea uses Cassandra interface that
connects to all nodes in a cluster at the same time. Any connectivity
issues should be handled by internal Cassandra mechanisms.
</para> </para>
<para> <para>
The number of milliseconds the server will wait between attempts to reconnect to the The number of milliseconds the server will wait between attempts to reconnect to the

7
doc/guide/dhcp6-srv.xml
View File

@@ -554,8 +554,7 @@ linkend="cassandra-database-configuration4"/> for details.</para>
purpose, be it lease or hosts information. This arrangement gives the most purpose, be it lease or hosts information. This arrangement gives the most
flexibility. Kea can keep leases and host reservations flexibility. Kea can keep leases and host reservations
separately, but can also point to the same database. Currently the separately, but can also point to the same database. Currently the
supported hosts database types are MySQL and PostgreSQL; the Cassandra supported hosts database types are MySQL, PostgreSQL and Cassandra.</para>
backend does not yet support host reservations.</para>
<para>For example, the following configuration can be used to <para>For example, the following configuration can be used to
configure connection to MySQL: configure connection to MySQL:
@@ -627,7 +626,9 @@ the host database after connectivity has been lost may be specified:
If the server is unable to reconnect to the database after making the maximum number If the server is unable to reconnect to the database after making the maximum number
of attempts the server will exit. A value of zero (the default) disables automatic of attempts the server will exit. A value of zero (the default) disables automatic
recovery and the server will exit immediately upon detecting a loss of connectivity recovery and the server will exit immediately upon detecting a loss of connectivity
(MySQL and Postgres only). (MySQL and Postgres only). For Cassandra, Kea uses Cassandra interface that
connects to all nodes in a cluster at the same time. Any connectivity
issues should be handled by internal Cassandra mechanisms.
</para> </para>
<para> <para>
The number of milliseconds the server will wait between attempts to reconnect to the The number of milliseconds the server will wait between attempts to reconnect to the