From 9ba89fa90587f3f9b329dafb60112ed2f5c27a32 Mon Sep 17 00:00:00 2001 From: "C. Scott Andreas" Date: Tue, 13 Dec 2011 14:55:45 -0800 Subject: [PATCH] Bump version to 0.2.0, updated Changelog. --- Changelog.md | 9 +++++++-- pom.xml | 2 +- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/Changelog.md b/Changelog.md index bdc2abe..a4fb054 100644 --- a/Changelog.md +++ b/Changelog.md @@ -1,9 +1,15 @@ # Ordasity Changelog ### Version History -#### Current: Ordasity 0.1.9 +#### Current: Ordasity 0.2.0 **Changes Since Previous Release:** +– Resolved a distributed race condition which can occur when using Ordasity's "handoff" capability at the very end of the process. + +– Resolved a case in which a node may fail to recognize that it has completed the claiming process after accepting handoff of a work unit from another node. + +#### Previous Releases: +###### Ordasity 0.1.9 :: – Resolved a case in which a node in an Ordasity cluster could find itself in a confused state after losing connection to a Zookeeper node, but successfully re-establishing the connection prior to the expiration of the Zookeeper session timeout. – Migrated node state information stored in Zookeeper from a flat string to structured JSON. @@ -11,6 +17,5 @@ Nodes running a previous version of Ordasity will see nodes running Ordasity 0.1.9+, but will view them in a "fallback" mode and operate under the safe assumption that the unrecognized nodes might not attempt to claim work. This safeguard ensures that all work units will remain claimed during the upgrade, but may result in 0.1.8 nodes claiming more than their fair share while it's in progress. As such, this release is safe for a rolling upgrade with no special treatment required. -#### Previous Releases: ###### Ordasity 0.1.8 :: Initial release \ No newline at end of file diff --git a/pom.xml b/pom.xml index 8b66464..7c11053 100644 --- a/pom.xml +++ b/pom.xml @@ -4,7 +4,7 @@ com.boundary ordasity - 0.1.9 + 0.2.0 Ordasity http://www.boundary.com