8.39. ctdb

Updated ctdb packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The ctdb packages provide a clustered database based on Samba's Trivial Database (TDB) used to store temporary data.
This update also fixes the following bugs:

Note

The ctdb package has been upgraded to upstream version 2.5.1, which provides a number of bug fixes and enhancements over the previous version. Note that due to these changes, the new version cannot run in parallel with the previous versions on the same cluster. In addition, note that to update CTDB in an existing cluster, CTDB has to be stopped on all nodes in the cluster before the upgrade can start. Furthermore, back up your cluster nodes in case the update fails. To ensure easy recovery in case of update failure, only a single node should be updated at a time. (BZ#1061630, BZ#1085447)
This update also fixes the following bugs:

Bug Fixes

BZ#987099
Prior to this update, CTDB sometimes waited too long for file locks to establish. Consequently, clients accessing a CTDB file-server cluster could time out due to high latency. With this update, the underlying code has been fixed to address the problem, and clients can now access files on a CTDB file-server cluster without timeouts.
BZ#1075913
Previously, when CTDB was configured to use two bonded interfaces, CTDB failed to assign an IP address to the second bonded interface. As a consequence, the cluster status of the cluster node was shown as "PARTIALLYONLINE" even when the actual status was "OK". The script which handles the network interfaces has been fixed and the cluster status now shows the correct value.
BZ#1085413
Prior to this update, CTDB under some circumstances attempted to free allocated memory at an invalid address which caused CTDB to terminate unexpectedly with a segmentation fault. This update fixes the underlying code and CTDB uses the correct address for freeing allocated memory. As a result, the crash no longer occurs.
The ctdb package has been upgraded to upstream version 2.5.1, which provides a number of bug fixes and enhancements over the previous version. Note that due to these changes, the new version cannot run in parallel with the previous versions on the same cluster. In addition, note that to update CTDB in an existing cluster, CTDB has to be stopped on all nodes in the cluster before the upgrade can start. Furthermore, back up your cluster nodes in case the update fails. To ensure easy recovery in case of update failure, only a single node should be updated at a time. (BZ#1061630, BZ#1085447)
Users of CTDB are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.