summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRonnie Sahlberg <ronniesahlberg@gmail.com>2009-09-29 13:31:41 +1000
committerRonnie Sahlberg <ronniesahlberg@gmail.com>2009-09-29 13:31:41 +1000
commit11c56dfd5663efbb116888dfc6d36e0b4badfb8a (patch)
tree7da026658d5cc89d88370ee471941894d5f89de7
parentc971d934a94be8676a7ece035ae1a0b963765464 (diff)
New version 1.0.91
(This used to be ctdb commit d1332f4d5d3d3e4b4e0cd362a6903d09e0d5fcbb)
-rw-r--r--ctdb/packaging/RPM/ctdb.spec9
1 files changed, 8 insertions, 1 deletions
diff --git a/ctdb/packaging/RPM/ctdb.spec b/ctdb/packaging/RPM/ctdb.spec
index 0954f74b05..5ddf8369b5 100644
--- a/ctdb/packaging/RPM/ctdb.spec
+++ b/ctdb/packaging/RPM/ctdb.spec
@@ -4,7 +4,7 @@ Summary: Clustered TDB
Vendor: Samba Team
Packager: Samba Team <samba@samba.org>
Name: ctdb
-Version: 1.0.90
+Version: 1.0.91
Release: 1
Epoch: 0
License: GNU GPL version 3
@@ -132,6 +132,13 @@ fi
%{_libdir}/pkgconfig/ctdb.pc
%changelog
+* Tue Sep 29 2009 : Version 1.0.91
+ - New vacuum and repack design from Wolgang Mueller.
+ - Add a new eventscript 01.reclock that will first mark a node unhealthy and later ban the node if the reclock file can not be accessed.
+ - Add machinereadable output to the ctdb getreclock command
+ - merge transaction updates from Michael Adam
+ - In the new banning code, reset the culprit count to 0 for all nodes that could successfully compelte a full recovery.
+ - dont mark the recovery master as a ban culprit because a node in the cluster needs a recovery. this happens naturally when using ctdb recover command so dont make this cause a node to be banned.
* Sat Sep 12 2009 : Version 1.0.90
- Be more forgiving for eventscripts that hang during startup
- Fix for a banning bug in the new banning logic