... | @@ -12,7 +12,7 @@ This release adds new features, improves existing features, clarifies documentat |
... | @@ -12,7 +12,7 @@ This release adds new features, improves existing features, clarifies documentat |
|
|
|
|
|
**DB cluster improvements.** Kea does not officially support any database (DB) clustering solutions; we have heard from users who have used clustering solutions with varying results. The ISC team has begun experimenting with Galera, Percona, NDB, and group replication. We set up clusters and ran unit and system tests, and found a few issues to address. The first two improvements make our MySQL libraries run better in a Percona cluster. One ticket updated the MySQL schema with the primary key for forensic logging (#1709), while another fixed several problems in unit tests that manifested themselves only on Percona (#1708). Finally, we are getting ready to run performance tests of multiple Kea instances connected to a DB cluster. To do that reliably, we need to export the list of leases assigned by each instance and then correlate them to check for any duplicates. With that in mind, we extended our `perfdhcp` tool with the ability to export the list of assigned leases. We hope to make good use of that capability in future tests. #1703
|
|
**DB cluster improvements.** Kea does not officially support any database (DB) clustering solutions; we have heard from users who have used clustering solutions with varying results. The ISC team has begun experimenting with Galera, Percona, NDB, and group replication. We set up clusters and ran unit and system tests, and found a few issues to address. The first two improvements make our MySQL libraries run better in a Percona cluster. One ticket updated the MySQL schema with the primary key for forensic logging (#1709), while another fixed several problems in unit tests that manifested themselves only on Percona (#1708). Finally, we are getting ready to run performance tests of multiple Kea instances connected to a DB cluster. To do that reliably, we need to export the list of leases assigned by each instance and then correlate them to check for any duplicates. With that in mind, we extended our `perfdhcp` tool with the ability to export the list of assigned leases. We hope to make good use of that capability in future tests. #1703
|
|
|
|
|
|
**Bug fixes.** Earlier Kea versions could experience a Kea crash when processing a high request rate while the forensic logging hook was configured to write log entries to a database and multi-threading was enabled. This release includes a fix for this problem (#1711). One user reported that Kea used values defined in client classes in a non-deterministic way. The code has been updated to provide consistent behavior for options and fixed fields (#1672). When dealing with client classification, it is possible to encounter a situation when there are subnets and pools available, but the client does not meet the class requirements and is therefore unable to use any of them. In such cases, earlier Kea versions printed cryptic error messages, such as `failed to allocate an IPv4 address after 0 attempt(s)`. This was confusing, so the message has been tweaked; several additional messages explain the reasons why the allocation failed. More details are available to debug the problem. #1701
|
|
**Bug fixes.** Earlier Kea versions could experience a crash when processing a high request rate while the forensic logging hook was configured to write log entries to a database and multi-threading was enabled. This release includes a fix for this problem (#1711). One user reported that Kea used values defined in client classes in a non-deterministic way. The code has been updated to provide consistent behavior for options and fixed fields (#1672). When dealing with client classification, it is possible to encounter a situation when there are subnets and pools available, but the client does not meet the class requirements and is therefore unable to use any of them. In such cases, earlier Kea versions printed cryptic error messages, such as `failed to allocate an IPv4 address after 0 attempt(s)`. This was confusing, so the message has been tweaked; several additional messages explain the reasons why the allocation failed. More details are available to debug the problem. #1701
|
|
|
|
|
|
**MySQL DB upgrade improvements.** Two prior development releases had incorrectly versioned database schema. As a result, when upgrading from 1.9.2 or 1.9.3 to 1.9.4 the `kea-admin` tool incorrectly assumed the schema was already updated, when in fact it was not. This is now corrected (#1698). Upgrading from any earlier Kea versions to 1.9.5 works correctly, and a workaround for upgrading to 1.9.4 is documented in the Known issues list. See the link below.
|
|
**MySQL DB upgrade improvements.** Two prior development releases had incorrectly versioned database schema. As a result, when upgrading from 1.9.2 or 1.9.3 to 1.9.4 the `kea-admin` tool incorrectly assumed the schema was already updated, when in fact it was not. This is now corrected (#1698). Upgrading from any earlier Kea versions to 1.9.5 works correctly, and a workaround for upgrading to 1.9.4 is documented in the Known issues list. See the link below.
|
|
|
|
|
... | | ... | |