[SCM] CTDB repository - branch 2.5 updated - ctdb-2.5.3-152-g1d4bd9e

[Amitay Isaacs]

The branch, 2.5 has been updated
       via  1d4bd9eb387775dca674112913c1bf23be1c3690 (commit)
      from  e1cc86972fa11bc22d202354db7786671b038dfe (commit)

http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=2.5


- Log -----------------------------------------------------------------
commit 1d4bd9eb387775dca674112913c1bf23be1c3690
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Mon Sep 22 11:54:04 2014 +1000

    doc: Update NEWS
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

-----------------------------------------------------------------------

Summary of changes:
 NEWS |   53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 53 insertions(+), 0 deletions(-)


Changeset truncated at 500 lines:

diff --git a/NEWS b/NEWS
index a91e48d..47d5b6c 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,56 @@
+Changes in CTDB 2.5.4
+=====================
+
+User-visible changes
+--------------------
+
+* New command "ctdb detach" to detach a database.
+
+* Support for TDB robust mutexes.  To enable set TDBMutexEnabled=1.
+  The setting is per node.
+
+* New manual page ctdb-statistics.7.
+
+Important bug fixes
+-------------------
+
+* Verify policy routing configuration when starting up to make sure that policy
+  routing tables do not override default routing tables.
+
+* "ctdb scriptstatus" should correctly list the number of scripts executed.
+
+* Do not run eventscripts at real-time priority.
+
+* Make sure "ctdb restoredb" and "ctdb wipedb" cannot affect an ongoing
+  recovery.
+
+* If a readonly record revokation fails, CTDB does not abort anymore.  It will
+  retry revoke.
+
+* pending_calls statistic now gets updated correctly.
+
+Important internal changes
+--------------------------
+
+* Vacuuming performance has been improved.
+
+* Fix the order of setting recovery mode and freezing databases.
+
+* Remove NAT gateway "monitor" event.
+
+* Add per database queue for lock requests.  This improves the lock
+  scheduling performance.
+
+* When processing dmaster packets (DMASTER_REQUEST and DMASTER_REPLY) defer all
+  call processing for that record.  This avoids the temporary inconsistency in
+  dmaster information which causes rapid bouncing of call request between two
+  nodes.
+
+* Correctly capture the output from lock helper processes, so it can be logged.
+
+* Many test improvements and additions.
+
+
 Changes in CTDB 2.5.3
 =====================
 


-- 
CTDB repository