The branch, 2.5 has been updated
       via  3394a2ecd858e54602c9bc577273c9a62ef7066f (commit)
      from  1e7f2597a64de43862564d54f566abfbeb3e4f28 (commit)

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


- Log -----------------------------------------------------------------
commit 3394a2ecd858e54602c9bc577273c9a62ef7066f
Author: Amitay Isaacs <[email protected]>
Date:   Mon Apr 13 14:17:12 2015 +1000

    doc: Update NEWS
    
    Signed-off-by: Amitay Isaacs <[email protected]>

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

Summary of changes:
 NEWS | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)


Changeset truncated at 500 lines:

diff --git a/NEWS b/NEWS
index 47d5b6c..580d853 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,49 @@
+Changes in CTDB 2.5.5
+=====================
+
+User-visible changes
+--------------------
+
+* Dump stack traces for hung RPC processes (mountd, rquotad, statd)
+
+* Add vaccuming latency to database statistics
+
+* Add -X option to ctdb tool that uses '|' as a separator to correctly handle
+  IPv6 addresses
+
+* Configuration variable VerifyRecoveryLock is now marked obsolete
+
+* Improved log messages when trying to set obsolete tunables
+
+Important bug fixes
+-------------------
+
+* Fix handling of IPv6 addresses
+
+* Use correct tdb flags when using robust mutex feature
+
+* Fix regression in client socket handling code
+
+* Fix regression in statd callout and make it more scalable
+
+* Change default log level to NOTICE, so the messages are correctly
+  displayed from CTDB tool
+
+Important internal changes
+--------------------------
+
+* Vacuuming performance improvements
+   - stagger multiple vacuuming child processes
+   - process all vacuum fetch requests in a loop
+
+* Improve handling of recovery lock
+
+* Many test improvements and additions.
+
+* Avoid logging every 10 seconds for locks that could not be obtained to 
prevent
+  flooding logs
+
+
 Changes in CTDB 2.5.4
 =====================
 


-- 
CTDB repository

Reply via email to